summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorBreno Leitao <leitao@debian.org>2025-02-06 14:05:53 +0300
committerDavid S. Miller <davem@davemloft.net>2025-02-10 18:04:17 +0300
commit4205f6495eea62c7f4042346e045e4ac706e1830 (patch)
tree9435a1f9f357a32e1ef927f8afd61a119e28cd8c /tools/perf/scripts/python/export-to-sqlite.py
parent1c1377d7b60c2d96eefab0bd9740d4a27fb0e1d3 (diff)
downloadlinux-4205f6495eea62c7f4042346e045e4ac706e1830.tar.xz
netconsole: Rename userdata to extradata
Rename "userdata" to "extradata" since this structure will hold both user and system data in future patches. Keep "userdata" term only for data that comes from userspace (configfs), while "extradata" encompasses both userdata and future kerneldata. These are the rules of the design 1. extradata_complete will hold userdata and sysdata (coming) 2. sysdata will come after userdata_length 3. extradata_complete[userdata_length] string will be replaced at every message 5. userdata is replaced when configfs changes (update_userdata()) 6. sysdata is replaced at every message Example: extradata_complete = "userkey=uservalue cpu=42" userdata_length = 17 sysdata_length = 7 (space (" ") is part of sysdata) Since sysdata is still not available, you will see the following in the send functions: extradata_len = nt->userdata_length; The upcoming patches will, which will add support for sysdata, will change it to: extradata_len = nt->userdata_length + sysdata_len; Signed-off-by: Breno Leitao <leitao@debian.org> Reviewed-by: Simon Horman <horms@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions