From: Florent Revest <revest@chromium.org>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
kpsingh@kernel.org, xukuohai@huaweicloud.com,
Florent Revest <revest@chromium.org>
Subject: [PATCH 0/2] Ftrace direct call samples improvements
Date: Thu, 27 Apr 2023 16:06:58 +0200 [thread overview]
Message-ID: <20230427140700.625241-1-revest@chromium.org> (raw)
This series is a subset of [1] that didn't go through the arm64 tree.
- The first patch fixes a small bug when a direct call sample is loaded on x86
- The second patch adds arm64 support to all direct calls samples
They are sent together because the second one depends on the first one.
This series applies cleanly on Linus's master branch. It needs the first two
patches of [1] which, at the time of writing, don't seem to have made it to the
trace/linux-trace tree but I suppose they could be pulled from Linus's master
1: https://lore.kernel.org/bpf/20230405180250.2046566-1-revest@chromium.org/
Florent Revest (2):
samples: ftrace: Save required argument registers in sample
trampolines
arm64: ftrace: Add direct call trampoline samples support
arch/arm64/Kconfig | 2 ++
samples/ftrace/ftrace-direct-modify.c | 34 ++++++++++++++++++
samples/ftrace/ftrace-direct-multi-modify.c | 40 +++++++++++++++++++++
samples/ftrace/ftrace-direct-multi.c | 24 +++++++++++++
samples/ftrace/ftrace-direct-too.c | 40 +++++++++++++++++----
samples/ftrace/ftrace-direct.c | 24 +++++++++++++
6 files changed, 158 insertions(+), 6 deletions(-)
--
2.40.1.495.gc816e09b53d-goog
next reply other threads:[~2023-04-27 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:06 Florent Revest [this message]
2023-04-27 14:06 ` [PATCH 1/2] samples: ftrace: Save required argument registers in sample trampolines Florent Revest
2023-04-27 14:07 ` [PATCH 2/2] arm64: ftrace: Add direct call trampoline samples support Florent Revest
2023-06-09 20:20 ` [PATCH 0/2] Ftrace direct call samples improvements Steven Rostedt
2023-06-10 8:28 ` Catalin Marinas
2023-07-10 21:40 ` 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=20230427140700.625241-1-revest@chromium.org \
--to=revest@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=xukuohai@huaweicloud.com \
/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).