From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Shuah Khan <shuah@kernel.org>, Tom Zanussi <zanussi@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 0/3] tracing: Support poll on event hist file
Date: Tue, 29 Oct 2024 10:03:56 +0900 [thread overview]
Message-ID: <20241029100356.099a6e639846aae4d0a6083f@kernel.org> (raw)
In-Reply-To: <172907575534.470540.12941248697563459082.stgit@mhiramat.roam.corp.google.com>
On Wed, 16 Oct 2024 19:49:15 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> Overview
> --------
> This patch set allows user to `poll`(or `select`, `epoll`) on event
> histogram interface. As you know each event has its own `hist` file
> which shows histograms generated by trigger action. So user can set
> a new hist trigger on any event you want to monitor, and poll on the
> `hist` file until it is updated.
Note: This `hist` is not disabled by tracing_on interface, because
that interface only disables `recording`.
Thus to monitor events via this interface, user must ensure the
tracing_on is enabled, also, set the same "filter" to the hist
action.
Thank you,
>
> There are 2 poll events are supported, POLLIN and POLLPRI. POLLIN
> means that there are any readable update on `hist` file and this
> event will be flashed only when you call read(). So, this is
> useful if you want to read the histogram periodically.
> The other POLLPRI event is for monitoring trace event. Like the
> POLLIN, this will be returned when the histogram is updated, but
> you don't need to read() the file and use poll() again.
>
> Note that this waits for histogram update (not event arrival), thus
> you must set a histogram on the event at first.
>
> Usage
> -----
> Here is an example usage:
>
> ----
> TRACEFS=/sys/kernel/tracing
> EVENT=$TRACEFS/events/sched/sched_process_free
>
> # setup histogram trigger and enable event
> echo "hist:key=comm" >> $EVENT/trigger
> echo 1 > $EVENT/enable
>
> # Wait for update
> poll pri $EVENT/hist
>
> # Event arrived.
> echo "process free event is comming"
> tail $TRACEFS/trace
> ----
>
> The 'poll' command is in the selftest patch.
>
> You can take this series also from here;
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git/log/?h=topic/event-hist-poll
>
> Thank you,
> ---
>
> Masami Hiramatsu (Google) (3):
> tracing/hist: Add poll(POLLIN) support on hist file
> tracing/hist: Support POLLPRI event for poll on histogram
> selftests/tracing: Add hist poll() support test
>
>
> include/linux/trace_events.h | 14 +++
> kernel/trace/trace_events.c | 14 +++
> kernel/trace/trace_events_hist.c | 100 +++++++++++++++++++-
> tools/testing/selftests/ftrace/Makefile | 2
> tools/testing/selftests/ftrace/poll.c | 74 +++++++++++++++
> .../ftrace/test.d/trigger/trigger-hist-poll.tc | 74 +++++++++++++++
> 6 files changed, 275 insertions(+), 3 deletions(-)
> create mode 100644 tools/testing/selftests/ftrace/poll.c
> create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-hist-poll.tc
>
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2024-10-29 1:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 10:49 [PATCH v6 0/3] tracing: Support poll on event hist file Masami Hiramatsu (Google)
2024-10-16 10:49 ` [PATCH v6 1/3] tracing/hist: Add poll(POLLIN) support on " Masami Hiramatsu (Google)
2024-12-19 16:23 ` Steven Rostedt
2024-12-27 3:04 ` Masami Hiramatsu
2024-10-16 10:49 ` [PATCH v6 2/3] tracing/hist: Support POLLPRI event for poll on histogram Masami Hiramatsu (Google)
2024-12-19 16:25 ` Steven Rostedt
2024-10-16 10:49 ` [PATCH v6 3/3] selftests/tracing: Add hist poll() support test Masami Hiramatsu (Google)
2024-12-19 16:04 ` Steven Rostedt
2024-12-27 1:30 ` Masami Hiramatsu
2024-10-29 1:03 ` Masami Hiramatsu [this message]
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=20241029100356.099a6e639846aae4d0a6083f@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=zanussi@kernel.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