From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Luigi Rizzo <rizzo@iet.unipi.it>,
bpf@vger.kernel.org, kpsingh@chromium.org, will@kernel.org
Subject: Re: arch_prepare_bpf_trampoline() for arm ?
Date: Thu, 25 Feb 2021 08:59:14 +0100 [thread overview]
Message-ID: <YDdY0gdKftxXZeMN@myrica> (raw)
In-Reply-To: <87blc92m5p.fsf@toke.dk>
On Wed, Feb 24, 2021 at 10:25:38PM +0100, Toke Høiland-Jørgensen wrote:
> Daniel Borkmann <daniel@iogearbox.net> writes:
>
> > On 2/24/21 8:54 PM, Luigi Rizzo wrote:
> >> I prepared a BPF version of kstats[1]
> >> https://github.com/luigirizzo/lr-cstats
> >> that uses fentry/fexit hooks to monitor the execution time
> >> of a kernel function.
> >>
> >> I hoped to have it working on ARM64 too, but it looks like
> >> arch_prepare_bpf_trampoline() only exists for x86.
> >>
> >> Is there any outstanding patch for this function on ARM64,
> >> or any similar function I could look at to implement it myself ?
> >
> > Not that I'm currently aware of, arm64 support would definitely be great
> > to have. From x86 side, the underlying arch dependency was basically on
> > text_poke_bp() to patch instructions on a live kernel. Haven't checked
> > recently whether an equivalent exists on arm64 yet, but perhaps Will
> > might know.
>
> Adding Jean-Philippe; I believe he is/was working on this...?
Yes, I have a very rough prototype here:
https://jpbrucker.net/git/linux/log/?h=bpf/devel
But not a ton of time to work on it at the moment, I don't know when I'll
be able to post something.
Thanks,
Jean
next prev parent reply other threads:[~2021-02-25 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:54 arch_prepare_bpf_trampoline() for arm ? Luigi Rizzo
2021-02-24 21:01 ` Daniel Borkmann
2021-02-24 21:25 ` Toke Høiland-Jørgensen
2021-02-25 7:59 ` Jean-Philippe Brucker [this message]
2021-02-24 21:30 ` KP Singh
2021-02-24 22:27 ` Daniel Borkmann
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=YDdY0gdKftxXZeMN@myrica \
--to=jean-philippe@linaro.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@chromium.org \
--cc=rizzo@iet.unipi.it \
--cc=toke@redhat.com \
--cc=will@kernel.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