From: adubey@linux.ibm.com
To: linuxppc-dev@lists.ozlabs.org
Cc: bpf@vger.kernel.org, hbathini@linux.ibm.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, maddy@linux.ibm.com,
Abhishek Dubey <adubey@linux.ibm.com>
Subject: [PATCH 1/4] powerpc64/bpf: Add support for instruction array
Date: Tue, 24 Feb 2026 20:09:29 -0500 [thread overview]
Message-ID: <20260225010950.20218-2-adubey@linux.ibm.com> (raw)
In-Reply-To: <20260225010950.20218-1-adubey@linux.ibm.com>
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")
Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>
---
arch/powerpc/net/bpf_jit_comp.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/powerpc/net/bpf_jit_comp.c b/arch/powerpc/net/bpf_jit_comp.c
index ebd21c75ce47..04f51f2c817c 100644
--- a/arch/powerpc/net/bpf_jit_comp.c
+++ b/arch/powerpc/net/bpf_jit_comp.c
@@ -379,6 +379,12 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *fp)
jit_data->hdr = hdr;
}
+ /*
+ * The bpf_prog_update_insn_ptrs function expects addrs to
+ * point to the first byte of the jitted instruction.
+ */
+ bpf_prog_update_insn_ptrs(fp, addrs, fimage);
+
out:
if (bpf_blinded)
bpf_jit_prog_release_other(fp, fp == org_fp ? tmp_fp : org_fp);
--
2.52.0
next prev parent reply other threads:[~2026-02-24 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 1:09 [PATCH 0/4] powerpc64/bpf: Add support for instruction array and indirect jump adubey
2026-02-25 1:09 ` adubey [this message]
2026-02-24 21:01 ` [PATCH 1/4] powerpc64/bpf: Add support for instruction array bot+bpf-ci
2026-02-25 1:09 ` [PATCH 2/4] selftest/bpf: Enable instruction array test for powerpc64 adubey
2026-02-25 1:09 ` [PATCH 3/4] powerpc64/bpf: Add support for indirect jump adubey
2026-02-25 1:09 ` [PATCH 4/4] selftest/bpf: Enable gotox tests for powerpc64 adubey
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=20260225010950.20218-2-adubey@linux.ibm.com \
--to=adubey@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--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