From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v6 0/2] Get trace buffer page size from kernel
Date: Wed, 26 Jan 2022 11:57:33 +0200 [thread overview]
Message-ID: <20220126095735.571222-1-tz.stoyanov@gmail.com> (raw)
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 v8 0/4] trace-cmd documentation update for v7 files"
https://lore.kernel.org/linux-trace-devel/20220126095530.571035-1-tz.stoyanov@gmail.com/
v6 changes:
- Code cleanups.
- Rebase.
v5 changes:
- Bug fixes.
- Code cleanups.
- Rebase.
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
.../trace-cmd/trace-cmd.dat.v7.5.txt | 1 +
lib/trace-cmd/include/trace-cmd-local.h | 4 +-
lib/trace-cmd/trace-input.c | 12 ++-
lib/trace-cmd/trace-output.c | 74 +++++++++++++++----
tracecmd/trace-dump.c | 9 ++-
5 files changed, 80 insertions(+), 20 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-26 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:57 Tzvetomir Stoyanov (VMware) [this message]
2022-01-26 9:57 ` [PATCH v6 1/2] trace-cmd library: Use the real trace buffer page size Tzvetomir Stoyanov (VMware)
2022-01-26 9:57 ` [PATCH v6 2/2] trace-cmd library: Introduce buffer page size per instance Tzvetomir Stoyanov (VMware)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220126095735.571222-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).