aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorAndrii Nakryiko <[email protected]>2021-07-20 13:49:25 -0700
committerAndrii Nakryiko <[email protected]>2021-07-20 13:49:26 -0700
commit807b8f0e24e6004984094e1bcbbd2b297011a085 (patch)
treef4b361833faca06c98dad5083ee32277498c23a6 /tools/perf/scripts/python
parent875fc315dbc3cdd3a5cab57b2bb7c1976ec8df44 (diff)
parent720c29fca9fb87c473148ff666b75314420cdda6 (diff)
Merge branch 'libbpf: btf typed data dumping fixes (__int128 usage, error propagation)'
Alan Maguire says: ==================== This series aims to resolve further issues with the BTF typed data dumping interfaces in libbpf. Compilation failures with use of __int128 on 32-bit platforms were reported [1]. As a result, the use of __int128 in libbpf typed data dumping is replaced with __u64 usage for bitfield manipulations. In the case of 128-bit integer values, they are simply split into two 64-bit hex values for display (patch 1). Tests are added for __int128 display in patch 2, using conditional compilation to avoid problems with a lack of __int128 support. Patch 3 resolves an issue Andrii noted about error propagation when handling enum data display. More followup work is required to ensure multi-dimensional char array display works correctly. [1] https://lore.kernel.org/bpf/[email protected]/T/#mc2cb023acfd6c3cd0b661e385787b76bb757430d Changes since v1: - added error handling for bitfield size > 64 bits by changing function signature for bitfield retrieval to return an int error value and to set bitfield value via a __u64 * argument (Andrii) ==================== Signed-off-by: Andrii Nakryiko <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions