diff options
| author |   Nathan Lynch <nathanl@linux.ibm.com> | 2024-02-02 18:26:46 -0600 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2024-02-05 17:01:25 +1100 |
| commit | 8ded03ae48b3657e0fbca99d8a9d8fa1bfb8c9be (patch) | |
| tree | 6955c0157b2b81c717f4f033443691820af05319 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Linux 6.8-rc2 (diff) | |
| download | linux-rng-8ded03ae48b3657e0fbca99d8a9d8fa1bfb8c9be.tar.xz linux-rng-8ded03ae48b3657e0fbca99d8a9d8fa1bfb8c9be.zip | |
powerpc/pseries/papr-sysparm: use u8 arrays for payloads
Some PAPR system parameter values are formatted by firmware as
nul-terminated strings (e.g. LPAR name, shared processor attributes).
But the values returned for other parameters, such as processor module
info and TLB block invalidate characteristics, are binary data with
parameter-specific layouts. So char[] isn't the appropriate type for
the general case. Use u8/__u8.
Signed-off-by: Nathan Lynch <nathanl@linux.ibm.com>
Fixes: 905b9e48786e ("powerpc/pseries/papr-sysparm: Expose character device to user space")
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20240202-papr-sysparm-ioblock-data-use-u8-v1-1-f5c6c89f65ec@linux.ibm.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions