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
Subject: [PATCH 0/3] ftrace: add sample code with dynamic ftrace_ops
Date: Thu, 3 Nov 2022 17:09:04 +0000 [thread overview]
Message-ID: <20221103170907.931465-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.
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:[~2022-11-03 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:09 Mark Rutland [this message]
2022-11-03 17:09 ` [PATCH 1/3] ftrace: maintain samples/ftrace Mark Rutland
2022-11-03 17:09 ` [PATCH 2/3] ftrace: export ftrace_free_filter() to modules Mark Rutland
2022-11-22 21:59 ` Steven Rostedt
2022-11-22 22:07 ` Steven Rostedt
2023-01-03 11:34 ` Mark Rutland
2022-11-03 17:09 ` [PATCH 3/3] ftrace: add sample with custom ops 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=20221103170907.931465-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-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
all inboxes | Powered by JetHome®