On 4/30/2019 3:54 AM, Jakub Kicinski wrote:
> On Mon, 29 Apr 2019 17:17:39 +0300, Aya Levin wrote:
>> In order to offline translate the raw memory into a human readable
>> format, the user can use some out-of-kernel scripts which receives as an
>> input the following:
>> - Object raw memory
>> - Driver object compiled with debug info (can be taken/generated at any time
>> from the machine)
>> - Object name
>
> Nice! IMHO this is more clean, precise and scalable than the fmsg stuff
> that we have now.
>
> Would you mind taking the string identifiers down a little bit more?
> "memory" could just have a first-class netlink attribute, it doesn't
> have to be this fake JSON string pair..
>
Thanks!
I am still using fmsg which is the API to construct JSON like output.
The fmg object contains the raw data.
I like your idea to remove the memory tag and just leave the array of
byte arrays. The SW dump devlink output without scripting is meaningless.
