From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] tracing/histograms: multiple hitcount support
Date: Thu, 25 Aug 2022 17:19:00 -0500 [thread overview]
Message-ID: <cover.1661464992.git.zanussi@kernel.org> (raw)
Hi Masami,
The first patch here adds support for multiple hitcount fields.
The second and third fix up your v2 [1] patches on top of the first
just so I could test them.
It works fine for me. Let me know if you want me to update the v3
version instead of this one and I can do that instead.
Thanks,
Tom
[1] https://lore.kernel.org/lkml/165966330764.3826604.9358384228095103695.stgit@devnote2/
The following changes since commit 09c9cdd023f26244463b1276b251a91e72915178:
tracing/filter: Call filter predicate functions directly via a switch statement (2022-08-23 17:41:13 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/masami-hitcount-v0
Masami Hiramatsu (Google) (2):
tracing: Add .percent suffix option to histogram values
tracing: Add .graph suffix option to histogram value
Tom Zanussi (1):
tracing: Allow multiple hitcount values in histograms
kernel/trace/trace.c | 3 +-
kernel/trace/trace_events_hist.c | 144 ++++++++++++++++++++++++++++---
2 files changed, 136 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-25 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:19 Tom Zanussi [this message]
2022-08-25 22:19 ` [PATCH 1/3] tracing: Allow multiple hitcount values in histograms Tom Zanussi
2022-08-25 22:19 ` [PATCH 2/3] tracing: Add .percent suffix option to histogram values Tom Zanussi
2022-08-25 22:19 ` [PATCH 3/3] tracing: Add .graph suffix option to histogram value Tom Zanussi
2022-08-26 0:58 ` [PATCH 0/3] tracing/histograms: multiple hitcount support Masami Hiramatsu
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=cover.1661464992.git.zanussi@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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.