From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] tracing: histogram internals doc, hist_debug, and misc
Date: Fri, 3 Apr 2020 14:31:18 -0500 [thread overview]
Message-ID: <cover.1585941485.git.zanussi@kernel.org> (raw)
Hi Steve,
Here's the histogram internals documentation I promised awhile back
(second patch).
Accompanying it is a new config option that enables a new hist_debug
event file, which is used by the examples in the doc to display
some of the histogram internals (third patch).
The first patch is just a cleanup suggested by Masami that I
previously missed.
Thanks,
Tom
The following changes since commit 8e99cf91b99bb30e16727f10ad6828741c0e992f:
tracing: Do not allocate buffer in trace_find_next_entry() in atomic (2020-04-03 11:30:50 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/hist-design-doc-v1
Tom Zanussi (3):
tracing: Check state.disabled in synth event trace functions
tracing: Add histogram-design document
tracing: Add hist_debug trace event files for histogram debugging
Documentation/trace/histogram-design.rst | 2115 ++++++++++++++++++++++
kernel/trace/Kconfig | 23 +
kernel/trace/trace.h | 1 +
kernel/trace/trace_events.c | 4 +
kernel/trace/trace_events_hist.c | 292 ++-
5 files changed, 2419 insertions(+), 16 deletions(-)
create mode 100644 Documentation/trace/histogram-design.rst
--
2.17.1
next reply other threads:[~2020-04-03 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 19:31 Tom Zanussi [this message]
2020-04-03 19:31 ` [PATCH 1/3] tracing: Check state.disabled in synth event trace functions Tom Zanussi
2020-04-03 19:31 ` [PATCH 2/3] tracing: Add histogram-design document Tom Zanussi
2020-04-03 19:31 ` [PATCH 3/3] tracing: Add hist_debug trace event files for histogram debugging Tom Zanussi
2020-05-18 18:35 ` [PATCH 0/3] tracing: histogram internals doc, hist_debug, and misc Tom Zanussi
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.1585941485.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox