From: Hari Bathini <hbathini@linux.ibm.com>
To: adubey@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, maddy@linux.ibm.com
Subject: Re: [PATCH v2 1/4] powerpc64/bpf: Add support for instruction array
Date: Tue, 31 Mar 2026 16:08:12 +0530 [thread overview]
Message-ID: <2fa9bd2a-6cee-4c59-a66d-049e503cea71@linux.ibm.com> (raw)
In-Reply-To: <20260227014315.39980-2-adubey@linux.ibm.com>
On 27/02/26 7:13 am, adubey@linux.ibm.com wrote:
> From: Abhishek Dubey <adubey@linux.ibm.com>
>
> On loading the BPF program, the verifier might adjust/omit some
> instructions. The adjusted instruction offset is accounted in the
> map containing original instruction -> xlated mapping. This patch
> add ppc64 JIT support to additionally build the xlated->jitted
> mapping for every instruction present in instruction array. This
> change is needed to enable support for indirect jumps, added in a
> subsequent patch.
>
> Invoke bpf_prog_update_insn_ptrs() with offset pair of xlated_offset
> and jited_offset. The offset mapping is already available, which is
> being used for bpf_prog_fill_jited_linfo() and can be directly used
> for bpf_prog_update_insn_ptrs() as well.
>
> Additional details present at:
>
> commit b4ce5923e780 ("bpf, x86: add new map type: instructions array")
>
Looks good to me. Except for a minor nit below..
Acked-by: Hari Bathini <hbathini@linux.ibm.com>
> Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
> ---
> arch/powerpc/net/bpf_jit_comp.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/powerpc/net/bpf_jit_comp.c b/arch/powerpc/net/bpf_jit_comp.c
> index 9ec5ab9b020e..620667c3400b 100644
> --- a/arch/powerpc/net/bpf_jit_comp.c
> +++ b/arch/powerpc/net/bpf_jit_comp.c
> @@ -373,6 +373,16 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *fp)
> goto out_addrs;
> }
> bpf_prog_fill_jited_linfo(fp, addrs);
> + /*
> + * On ABI V1, executable code starts after the function
> + * descriptor, so adjust base accordingly.
> + */
> +#ifdef CONFIG_PPC64_ELF_ABI_V1
> + bpf_prog_update_insn_ptrs(fp, addrs,
> + (void *)fimage + FUNCTION_DESCR_SIZE);
> +#else
> + bpf_prog_update_insn_ptrs(fp, addrs, fimage);
> +#endif
You don't need this ifdeffery as FUNCTION_DESCR_SIZE is already defined
based on this CONFIG option.
- Hari
next prev parent reply other threads:[~2026-03-31 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 1:43 [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump adubey
2026-02-27 1:43 ` [PATCH v2 1/4] powerpc64/bpf: Add support for instruction array adubey
2026-03-31 10:38 ` Hari Bathini [this message]
2026-02-27 1:43 ` [PATCH v2 2/4] selftest/bpf: Enable instruction array test for powerpc64 adubey
2026-02-27 1:43 ` [PATCH v2 3/4] powerpc64/bpf: Add support for indirect jump adubey
2026-03-31 10:42 ` Hari Bathini
2026-02-27 1:43 ` [PATCH v2 4/4] selftest/bpf: Enable gotox tests for powerpc64 adubey
2026-02-27 15:28 ` [PATCH v2 0/4] powerpc64/bpf: Add support for instruction array and indirect jump Venkat
2026-03-03 5:12 ` Venkat Rao Bagalkote
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=2fa9bd2a-6cee-4c59-a66d-049e503cea71@linux.ibm.com \
--to=hbathini@linux.ibm.com \
--cc=adubey@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.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