From: Mark Rutland <mark.rutland@arm.com>
To: linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, mhiramat@kernel.org, revest@chromium.org,
rostedt@goodmis.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] ftrace: Add sample code with dynamic ftrace_ops
Date: Tue, 3 Jan 2023 12:49:09 +0000 [thread overview]
Message-ID: <20230103124912.2948963-1-mark.rutland@arm.com> (raw)
This series adds sample code to manipulate dynamic ftrace_ops, which
I've been using to benchmark/test some changes I've been making in this
area for arm64.
In the process of writing that I spotted a couple of minor issues,
addressed by the first two patches.
I'm not sure whether this should be a sample or something under lib/;
I'm happy to change that if folk have strong opinions.
Since v1 [1]:
* Rebase to v6.2-rc2 (trivial)
* Fix typos
* Fix commit title style
* Apply Steve's Reviewed-by to patch 2
* Fix "save_regs" module parameter name
* Add example output from sample module
[1] https://lore.kernel.org/lkml/20221103170907.931465-1-mark.rutland@arm.com/
Thanks,
Mark.
Mark Rutland (3):
ftrace: Maintain samples/ftrace
ftrace: Export ftrace_free_filter() to modules
ftrace: Add sample with custom ops
MAINTAINERS | 1 +
kernel/trace/ftrace.c | 23 +-
samples/Kconfig | 7 +
samples/Makefile | 1 +
samples/ftrace/Makefile | 1 +
samples/ftrace/ftrace-direct-multi-modify.c | 1 +
samples/ftrace/ftrace-direct-multi.c | 1 +
samples/ftrace/ftrace-ops.c | 252 ++++++++++++++++++++
8 files changed, 286 insertions(+), 1 deletion(-)
create mode 100644 samples/ftrace/ftrace-ops.c
--
2.30.2
next reply other threads:[~2023-01-03 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:49 Mark Rutland [this message]
2023-01-03 12:49 ` [PATCH v2 1/3] ftrace: Maintain samples/ftrace Mark Rutland
2023-01-04 14:31 ` Masami Hiramatsu
2023-01-03 12:49 ` [PATCH v2 2/3] ftrace: Export ftrace_free_filter() to modules Mark Rutland
2023-01-04 14:51 ` Masami Hiramatsu
2023-01-04 15:30 ` Mark Rutland
2023-01-04 16:03 ` Steven Rostedt
2023-01-03 12:49 ` [PATCH v2 3/3] ftrace: Add sample with custom ops Mark Rutland
2023-01-04 14:56 ` Masami Hiramatsu
2023-02-06 22:25 ` Guenter Roeck
2023-02-07 9:33 ` Mark Rutland
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=20230103124912.2948963-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=revest@chromium.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;
as well as URLs for NNTP newsgroup(s).