From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: [PATCH v2 0/2] tracing: Make synthetic events a separate option
Date: Thu, 28 May 2020 14:32:36 -0500 [thread overview]
Message-ID: <cover.1590693308.git.zanussi@kernel.org> (raw)
Hi Steve,
These are the same patches as v1, but after posting v1 I realized that
if you applied them on top of the other patchset I posted awhile back
("[PATCH 0/3] tracing: histogram internals doc, hist_debug, and misc")
[1], you wouldn't be able to apply these.
So assuming you apply the other patchset first, these should apply
cleanly on top of those.
Thanks,
Tom
[1] https://lore.kernel.org/lkml/cover.1585941485.git.zanussi@kernel.org/
v1 text:
Since synthetic events can now be used separately from hist triggers,
it makes sense to actually separate them into different options. It
also makes sense in terms of file bloat - trace_events_hist.c was
getting very large and this makes it smaller and easier to follow.
Thanks,
Tom
The following changes since commit 77914c22b0ba493d9783c53bbfbc6087d6a7e1b1:
tracing: Add hist_debug trace event files for histogram debugging (2020-04-03 13:46:05 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/separate-synth-v2
Tom Zanussi (2):
tracing: Move synthetic events to a separate file
selftests/ftrace: Distinguish between hist and synthetic event checks
kernel/trace/Kconfig | 20 +-
kernel/trace/Makefile | 1 +
kernel/trace/trace_events_hist.c | 2071 ++---------------
kernel/trace/trace_events_synth.c | 1789 ++++++++++++++
kernel/trace/trace_synth.h | 36 +
.../trigger-field-variable-support.tc | 5 +
.../trigger-inter-event-combined-hist.tc | 5 +
.../trigger-multi-actions-accept.tc | 5 +
.../trigger-onmatch-action-hist.tc | 5 +
.../trigger-onmatch-onmax-action-hist.tc | 5 +
.../inter-event/trigger-onmax-action-hist.tc | 5 +
.../trigger-snapshot-action-hist.tc | 5 +
.../inter-event/trigger-trace-action-hist.tc | 5 +
13 files changed, 2029 insertions(+), 1928 deletions(-)
create mode 100644 kernel/trace/trace_events_synth.c
create mode 100644 kernel/trace/trace_synth.h
--
2.17.1
next reply other threads:[~2020-05-28 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 19:32 Tom Zanussi [this message]
2020-05-28 19:32 ` [PATCH v2 1/2] tracing: Move synthetic events to a separate file Tom Zanussi
2020-05-28 19:32 ` [PATCH v2 2/2] selftests/ftrace: Distinguish between hist and synthetic event checks Tom Zanussi
2020-05-29 14:38 ` Masami Hiramatsu
2020-05-29 14:53 ` Steven Rostedt
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.1590693308.git.zanussi@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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.