The trace buffer page size is equal to the system memory page size in the current ftrace implementation, but this may change in the future. The newly introduced traceevent library API should be used to get the real trace buffer page size, bases on the information from the "events/header_page" ftrace file. This patch set depends on: "[PATCH] libtraceevent: A new API for trace page size" https://lore.kernel.org/linux-trace-devel/20211126034606.190816-1-tz.stoyanov@xxxxxxxxx/ "[PATCH v6 00/11] trace-cmd dump - v7 update" https://lore.kernel.org/linux-trace-devel/20211210110511.98856-1-tz.stoyanov@xxxxxxxxx/ v4 changes - Rebased on top of the latest master. v3 changes - Rebased on top of the latest master. v2 changes: - libtraceevent API is renamed, use the new version. - Rewrote get_trace_page_size() to use libtracefs APIs. - Cleanups in "trace-cmd dump" output, related to buffer page size print. Tzvetomir Stoyanov (VMware) (2): trace-cmd library: Use the real trace buffer page size trace-cmd library: Introduce buffer page size per instance lib/trace-cmd/include/trace-cmd-local.h | 4 +- lib/trace-cmd/trace-input.c | 11 +++- lib/trace-cmd/trace-output.c | 71 ++++++++++++++++++++----- tracecmd/trace-dump.c | 9 +++- 4 files changed, 77 insertions(+), 18 deletions(-) -- 2.33.1
|