From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] tracing: Add and use event_command parsing func helpers
Date: Fri, 12 Nov 2021 14:23:38 -0600 [thread overview]
Message-ID: <cover.1636748267.git.zanussi@kernel.org> (raw)
With more event commands being implemented, it's been pointed out that
it would make sense to clean up the existing ones and make it easier
to implement new ones without copying a lot of boilerplate. The main
culprit here is the event_command.func() callback - the rest of the
event_command infrastructure has default implementations that work for
most implementations. The func() callback is a little different in
that every new command needs to customize parsing to some extent.
This patchset attempts to help clean that up and make it easier for
new users to deal with.
v2: removed unused event_trigger_remove(). No change in functionality.
The following changes since commit 67d4f6e3bf5dddced226fbf19704cdbbb0c98847:
ftrace/samples: Add missing prototype for my_direct_func (2021-11-01 20:56:51 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/cleanup-hist-func-v2
Tom Zanussi (2):
tracing: Add helper functions to simplify event_command callback
handling
tracing: Have existing event_command implementations use helpers
kernel/trace/trace.h | 21 ++
kernel/trace/trace_events_hist.c | 52 ++---
kernel/trace/trace_events_trigger.c | 294 ++++++++++++++++------------
3 files changed, 208 insertions(+), 159 deletions(-)
--
2.17.1
next reply other threads:[~2021-11-12 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 20:23 Tom Zanussi [this message]
2021-11-12 20:23 ` [PATCH v2 1/2] tracing: Add helper functions to simplify event_command callback handling Tom Zanussi
2021-11-16 21:41 ` Steven Rostedt
2021-11-16 21:59 ` Tom Zanussi
2021-11-12 20:23 ` [PATCH v2 2/2] tracing: Have existing event_command implementations use helpers 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.1636748267.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