From: Xu Kuohai <xukuohai@huawei.com>
To: Florent Revest <revest@chromium.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>, <bpf@vger.kernel.org>
Cc: <catalin.marinas@arm.com>, <will@kernel.org>,
<rostedt@goodmis.org>, <mhiramat@kernel.org>,
<mark.rutland@arm.com>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <kpsingh@kernel.org>, <jolsa@kernel.org>,
<xukuohai@huaweicloud.com>
Subject: Re: [PATCH 0/8] Add ftrace direct call for arm64
Date: Thu, 2 Feb 2023 16:36:36 +0800 [thread overview]
Message-ID: <85af713d-00fe-b113-1331-1a44480c016f@huawei.com> (raw)
In-Reply-To: <20230201163420.1579014-1-revest@chromium.org>
On 2/2/2023 12:34 AM, Florent Revest wrote:
> This series adds ftrace direct call support to arm64.
> This makes BPF tracing programs (fentry/fexit/fmod_ret/lsm) work on arm64.
>
> It is meant to apply on top of the arm64 tree which contains Mark Rutland's
> series on CALL_OPS [1] under the for-next/ftrace tag.
> > The first three patches consolidate the two existing ftrace APIs for registering
> direct calls. They are split to make the reviewers lives easier but if it'd be a
> preferred style, I'd be happy to squash them in the next revision.
> Currently, there is both a _ftrace_direct and _ftrace_direct_multi API. Apart
> from samples and selftests, there are no users of the _ftrace_direct API left
> in-tree so this deletes it and renames the _ftrace_direct_multi API to
> _ftrace_direct for simplicity.
>
> The main benefit of this refactoring is that, with the API that's left, an
> ftrace_ops backing a direct call will only ever point to one direct call. We can
> therefore store the direct called trampoline address in the ops (patch 4) and
> look it up from the ftrace trampoline on arm64 (patch 7) in the case when the
> destination would be out of reach of a BL instruction at the ftrace callsite.
> (in this case, ftrace_caller acts as a lightweight intermediary trampoline)
>
> This series has been tested on both arm64 and x86_64 with:
> 1- CONFIG_FTRACE_SELFTEST (cf: patch 6)
> 2- samples/ftrace/*.ko (cf: patch 8)
> 3- tools/testing/selftests/bpf/test_progs (both -t lsm and -t fentry_fexit)
so it's time to update DENYLIST.aarch64 to unblock tests that failed due to lack of direct call.
>
> This follows up on prior art by Xu Kuohai [2].
> The implementation here is totally different but the fix for ftrace selftests
> (patch 6) is a trivial rebase of a patch originally by Xu so I kept his
> authorship and trailers untouched on that patch, I hope that's ok. >
that's ok for me, thanks.
> 1: https://lore.kernel.org/all/20230123134603.1064407-1-mark.rutland@arm.com/
> 2: https://lore.kernel.org/bpf/20220913162732.163631-1-xukuohai@huaweicloud.com/
>
> Florent Revest (7):
> ftrace: Replace uses of _ftrace_direct APIs with _ftrace_direct_multi
> ftrace: Remove the legacy _ftrace_direct API
> ftrace: Rename _ftrace_direct_multi APIs to _ftrace_direct APIs
> ftrace: Store direct called addresses in their ops
> ftrace: Make DIRECT_CALLS work WITH_ARGS and !WITH_REGS
> arm64: ftrace: Add direct call support
> arm64: ftrace: Add direct called trampoline samples support
>
> Xu Kuohai (1):
> ftrace: Fix dead loop caused by direct call in ftrace selftest
>
> arch/arm64/Kconfig | 4 +
> arch/arm64/include/asm/ftrace.h | 24 ++
> arch/arm64/kernel/asm-offsets.c | 6 +
> arch/arm64/kernel/entry-ftrace.S | 70 +++-
> arch/arm64/kernel/ftrace.c | 36 +-
> include/linux/ftrace.h | 51 +--
> kernel/bpf/trampoline.c | 14 +-
> kernel/trace/Kconfig | 2 +-
> kernel/trace/ftrace.c | 433 +-------------------
> kernel/trace/trace_selftest.c | 14 +-
> samples/Kconfig | 2 +-
> samples/ftrace/ftrace-direct-modify.c | 41 +-
> samples/ftrace/ftrace-direct-multi-modify.c | 44 +-
> samples/ftrace/ftrace-direct-multi.c | 28 +-
> samples/ftrace/ftrace-direct-too.c | 35 +-
> samples/ftrace/ftrace-direct.c | 33 +-
> 16 files changed, 333 insertions(+), 504 deletions(-)
>
next prev parent reply other threads:[~2023-02-02 8:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:34 Florent Revest
2023-02-01 16:34 ` [PATCH 1/8] ftrace: Replace uses of _ftrace_direct APIs with _ftrace_direct_multi Florent Revest
2023-02-02 15:01 ` Mark Rutland
2023-02-02 17:37 ` Florent Revest
2023-02-07 15:21 ` Florent Revest
2023-02-07 15:35 ` Steven Rostedt
2023-02-07 16:19 ` Florent Revest
2023-02-01 16:34 ` [PATCH 2/8] ftrace: Remove the legacy _ftrace_direct API Florent Revest
2023-02-02 15:11 ` Mark Rutland
2023-02-01 16:34 ` [PATCH 3/8] ftrace: Rename _ftrace_direct_multi APIs to _ftrace_direct APIs Florent Revest
2023-02-02 15:17 ` Mark Rutland
2023-02-01 16:34 ` [PATCH 4/8] ftrace: Store direct called addresses in their ops Florent Revest
2023-02-02 15:29 ` Mark Rutland
2023-02-02 17:41 ` Florent Revest
2023-02-01 16:34 ` [PATCH 5/8] ftrace: Make DIRECT_CALLS work WITH_ARGS and !WITH_REGS Florent Revest
2023-02-02 15:54 ` Mark Rutland
2023-02-02 16:56 ` Mark Rutland
2023-02-02 18:19 ` Florent Revest
2023-02-03 10:03 ` Mark Rutland
2023-02-03 11:01 ` Florent Revest
2023-02-02 18:18 ` Florent Revest
2023-02-01 16:34 ` [PATCH 6/8] ftrace: Fix dead loop caused by direct call in ftrace selftest Florent Revest
2023-02-02 19:03 ` Mark Rutland
2023-02-03 12:35 ` Florent Revest
2023-02-03 15:37 ` Mark Rutland
2023-02-06 16:25 ` Florent Revest
2023-02-01 16:34 ` [PATCH 7/8] arm64: ftrace: Add direct call support Florent Revest
2023-02-03 15:34 ` Mark Rutland
2023-02-06 16:25 ` Florent Revest
2023-02-01 16:34 ` [PATCH 8/8] arm64: ftrace: Add direct called trampoline samples support Florent Revest
2023-02-02 8:36 ` Xu Kuohai [this message]
2023-02-02 10:50 ` [PATCH 0/8] Add ftrace direct call for arm64 Daniel Borkmann
2023-02-02 17:32 ` Florent Revest
2023-02-02 20:06 ` Steven Rostedt
2023-02-03 9:49 ` 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=85af713d-00fe-b113-1331-1a44480c016f@huawei.com \
--to=xukuohai@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.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=revest@chromium.org \
--cc=rostedt@goodmis.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®