From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] tracing: Make synthetic events a separate option
Date: Wed, 27 May 2020 14:53:46 -0500 [thread overview]
Message-ID: <cover.1590608239.git.zanussi@kernel.org> (raw)
Hi Steve,
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 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/separate-synth-v1
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 | 2082 ++---------------
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, 2028 insertions(+), 1940 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-27 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 19:53 Tom Zanussi [this message]
2020-05-27 19:53 ` [PATCH 1/2] tracing: Move synthetic events to a separate file Tom Zanussi
2020-05-27 19:53 ` [PATCH 2/2] selftests/ftrace: Distinguish between hist and synthetic event checks 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.1590608239.git.zanussi@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).