From: Jon Hunter <jonathanh@nvidia.com>
To: Xu Kuohai <xukuohai@huawei.com>,
bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Will Deacon <will@kernel.org>, KP Singh <kpsingh@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Zi Shen Lim <zlim.lnx@gmail.com>, Martin KaFai Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
James Morse <james.morse@arm.com>, Hou Tao <houtao1@huawei.com>,
Jason Wang <wangborong@cdjrlc.com>
Subject: Re: [PATCH bpf-next v9 3/4] bpf, arm64: Implement bpf_arch_text_poke() for arm64
Date: Mon, 18 Jul 2022 14:52:52 +0100 [thread overview]
Message-ID: <8de014c1-aa63-5783-e5fd-53b7fdece805@nvidia.com> (raw)
In-Reply-To: <20220711150823.2128542-4-xukuohai@huawei.com>
On 11/07/2022 16:08, Xu Kuohai wrote:
> Implement bpf_arch_text_poke() for arm64, so bpf prog or bpf trampoline
> can be patched with it.
>
> When the target address is NULL, the original instruction is patched to a
> NOP.
>
> When the target address and the source address are within the branch
> range, the original instruction is patched to a bl instruction to the
> target address directly.
>
> To support attaching bpf trampoline to both regular kernel function and
> bpf prog, we follow the ftrace patchsite way for bpf prog. That is, two
> instructions are inserted at the beginning of bpf prog, the first one
> saves the return address to x9, and the second is a nop which will be
> patched to a bl instruction when a bpf trampoline is attached.
>
> However, when a bpf trampoline is attached to bpf prog, the distance
> between target address and source address may exceed 128MB, the maximum
> branch range, because bpf trampoline and bpf prog are allocated
> separately with vmalloc. So long jump should be handled.
>
> When a bpf prog is constructed, a plt pointing to empty trampoline
> dummy_tramp is placed at the end:
>
> bpf_prog:
> mov x9, lr
> nop // patchsite
> ...
> ret
>
> plt:
> ldr x10, target
> br x10
> target:
> .quad dummy_tramp // plt target
>
> This is also the state when no trampoline is attached.
>
> When a short-jump bpf trampoline is attached, the patchsite is patched to
> a bl instruction to the trampoline directly:
>
> bpf_prog:
> mov x9, lr
> bl <short-jump bpf trampoline address> // patchsite
> ...
> ret
>
> plt:
> ldr x10, target
> br x10
> target:
> .quad dummy_tramp // plt target
>
> When a long-jump bpf trampoline is attached, the plt target is filled with
> the trampoline address and the patchsite is patched to a bl instruction to
> the plt:
>
> bpf_prog:
> mov x9, lr
> bl plt // patchsite
> ...
> ret
>
> plt:
> ldr x10, target
> br x10
> target:
> .quad <long-jump bpf trampoline address>
>
> dummy_tramp is used to prevent another CPU from jumping to an unknown
> location during the patching process, making the patching process easier.
>
> The patching process is as follows:
>
> 1. when neither the old address or the new address is a long jump, the
> patchsite is replaced with a bl to the new address, or nop if the new
> address is NULL;
>
> 2. when the old address is not long jump but the new one is, the
> branch target address is written to plt first, then the patchsite
> is replaced with a bl instruction to the plt;
>
> 3. when the old address is long jump but the new one is not, the address
> of dummy_tramp is written to plt first, then the patchsite is replaced
> with a bl to the new address, or a nop if the new address is NULL;
>
> 4. when both the old address and the new address are long jump, the
> new address is written to plt and the patchsite is not changed.
>
> Signed-off-by: Xu Kuohai <xukuohai@huawei.com>
> Acked-by: Song Liu <songliubraving@fb.com>
> Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com>
> Reviewed-by: KP Singh <kpsingh@kernel.org>
> Reviewed-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> arch/arm64/net/bpf_jit.h | 7 +
> arch/arm64/net/bpf_jit_comp.c | 329 ++++++++++++++++++++++++++++++++--
> 2 files changed, 322 insertions(+), 14 deletions(-)
This change appears to be causing the build to fail ...
/tmp/cc52xO0c.s: Assembler messages:
/tmp/cc52xO0c.s:8: Error: operand 1 should be an integer register -- `mov lr,x9'
/tmp/cc52xO0c.s:7: Error: undefined symbol lr used as an immediate value
make[2]: *** [scripts/Makefile.build:250: arch/arm64/net/bpf_jit_comp.o] Error 1
make[1]: *** [scripts/Makefile.build:525: arch/arm64/net] Error 2
Let me know if you have any thoughts.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2022-07-18 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 15:08 [PATCH bpf-next v9 0/4] bpf trampoline for arm64 Xu Kuohai
2022-07-11 15:08 ` [PATCH bpf-next v9 1/4] bpf: Remove is_valid_bpf_tramp_flags() Xu Kuohai
2022-07-11 15:08 ` [PATCH bpf-next v9 2/4] arm64: Add LDR (literal) instruction Xu Kuohai
2022-07-11 15:08 ` [PATCH bpf-next v9 3/4] bpf, arm64: Implement bpf_arch_text_poke() for arm64 Xu Kuohai
2022-07-18 13:52 ` Jon Hunter [this message]
2022-07-18 15:37 ` Xu Kuohai
2022-07-21 7:29 ` Jon Hunter
2022-07-11 15:08 ` [PATCH bpf-next v9 4/4] bpf, arm64: bpf trampoline " Xu Kuohai
2022-07-11 19:10 ` [PATCH bpf-next v9 0/4] " patchwork-bot+netdevbpf
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=8de014c1-aa63-5783-e5fd-53b7fdece805@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=hawk@kernel.org \
--cc=houtao1@huawei.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=wangborong@cdjrlc.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xukuohai@huawei.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
--cc=zlim.lnx@gmail.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