All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v3 0/2] Get trace buffer page size from kernel
Date: Thu,  2 Dec 2021 14:32:58 +0200	[thread overview]
Message-ID: <20211202123300.44401-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] libtraceevent: A new API for trace page size"
  https://lore.kernel.org/linux-trace-devel/20211126034606.190816-1-tz.stoyanov@gmail.com/
 "[PATCH v5 00/10] trace-cmd dump - v7 update" patch set.
  https://lore.kernel.org/linux-trace-devel/20211202122907.44008-1-tz.stoyanov@gmail.com/

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


             reply	other threads:[~2021-12-02 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 12:32 Tzvetomir Stoyanov (VMware) [this message]
2021-12-02 12:32 ` [PATCH v3 1/2] trace-cmd library: Use the real trace buffer page size Tzvetomir Stoyanov (VMware)
2021-12-02 12:33 ` [PATCH v3 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=20211202123300.44401-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.