bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Protopopov <a.s.protopopov@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Anton Protopopov <aspsk@isovalent.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Quentin Monnet <qmo@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH v6 bpf-next 04/17] bpf, x86: add new map type: instructions array
Date: Tue, 21 Oct 2025 18:32:40 +0000	[thread overview]
Message-ID: <aPfRyNQVP53swJ0l@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQLOtQWMb4eOtLXyXhWrkPV8DKdYajb+DbG=sSucEbtJFw@mail.gmail.com>

On 25/10/21 10:49AM, Alexei Starovoitov wrote:
> On Sun, Oct 19, 2025 at 1:15 PM Anton Protopopov
> <a.s.protopopov@gmail.com> wrote:
> > diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c
> > index d4c93d9e73e4..c8e628410d2c 100644
> > --- a/arch/x86/net/bpf_jit_comp.c
> > +++ b/arch/x86/net/bpf_jit_comp.c
> > @@ -1691,6 +1691,7 @@ static int do_jit(struct bpf_prog *bpf_prog, int *addrs, u8 *image, u8 *rw_image
> >         prog = temp;
> >
> >         for (i = 1; i <= insn_cnt; i++, insn++) {
> > +               u32 abs_xlated_off = bpf_prog->aux->subprog_start + i - 1;
> >                 const s32 imm32 = insn->imm;
> >                 u32 dst_reg = insn->dst_reg;
> >                 u32 src_reg = insn->src_reg;
> > @@ -2751,6 +2752,13 @@ st:                      if (is_imm8(insn->off))
> >                                 return -EFAULT;
> >                         }
> >                         memcpy(rw_image + proglen, temp, ilen);
> > +
> > +                       /*
> > +                        * Instruction arrays need to know how xlated code
> > +                        * maps to jitted code
> > +                        */
> > +                       bpf_prog_update_insn_ptr(bpf_prog, abs_xlated_off, proglen,
> > +                                                image + proglen);
> 
> ...
> 
> > +void bpf_prog_update_insn_ptr(struct bpf_prog *prog,
> > +                             u32 xlated_off,
> > +                             u32 jitted_off,
> > +                             void *jitted_ip)
> > +{
> > +       struct bpf_insn_array *insn_array;
> > +       struct bpf_map *map;
> > +       int i, j;
> > +
> > +       for (i = 0; i < prog->aux->used_map_cnt; i++) {
> > +               map = prog->aux->used_maps[i];
> > +               if (!is_insn_array(map))
> > +                       continue;
> > +
> > +               insn_array = cast_insn_array(map);
> > +               for (j = 0; j < map->max_entries; j++) {
> > +                       if (insn_array->ptrs[j].user_value.xlated_off == xlated_off) {
> > +                               insn_array->ips[j] = (long)jitted_ip;
> > +                               insn_array->ptrs[j].jitted_ip = jitted_ip;
> > +                               insn_array->ptrs[j].user_value.jitted_off = jitted_off;
> > +                       }
> > +               }
> > +       }
> > +}
> 
> This algorithm doesn't scale.
> You're calling bpf_prog_update_insn_ptr() for every insn
> and doing it as many times as they're JIT passes.
> There could be up to 20 passes and hundreds of thousands of insns.
> x86 JIT already keeps the mapping from insn to IP in jit_datat->addrs[].
> Use it. Roughly like:
> insn_array = cast_insn_array(map);
> for (j = 0; j < map->max_entries; j++) {
>    ip = addrs[insn_array->ptrs[j].user_value.xlated_off -
> subprog_start] + image;
> And this is done once per insn_array after JIT is done.

Thanks! Will do.

  reply	other threads:[~2025-10-21 18:26 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-19 20:21 [PATCH v6 bpf-next 00/17] BPF indirect jumps Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 01/17] bpf: fix the return value of push_stack Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 02/17] bpf: save the start of functions in bpf_prog_aux Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 03/17] bpf: generalize and export map_get_next_key for arrays Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 04/17] bpf, x86: add new map type: instructions array Anton Protopopov
2025-10-21 17:49   ` Alexei Starovoitov
2025-10-21 18:32     ` Anton Protopopov [this message]
2025-10-21 23:26   ` Eduard Zingerman
2025-10-24 12:12     ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 05/17] selftests/bpf: add selftests for new insn_array map Anton Protopopov
2025-10-21 23:51   ` Eduard Zingerman
2025-10-22 13:44     ` Anton Protopopov
2025-10-22 13:55       ` Eduard Zingerman
2025-10-22 14:06         ` Anton Protopopov
2025-10-22 14:03           ` Eduard Zingerman
2025-10-22 14:13             ` Anton Protopopov
2025-10-22 17:00             ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 06/17] bpf: support instructions arrays with constants blinding Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 07/17] selftests/bpf: test instructions arrays with blinding Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 08/17] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-10-20  8:38   ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 09/17] bpf: make bpf_insn_successors to return a pointer Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 10/17] bpf, x86: add support for indirect jumps Anton Protopopov
2025-10-20  7:23   ` Anton Protopopov
2025-10-21 21:17   ` Eduard Zingerman
2025-10-22  6:51     ` Anton Protopopov
2025-10-22  6:53       ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 11/17] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-10-21 21:19   ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 12/17] bpf, docs: do not state that indirect jumps are not supported Anton Protopopov
2025-10-21 19:15   ` Eduard Zingerman
2025-10-21 19:32     ` Anton Protopopov
2025-10-21 19:36       ` Eduard Zingerman
2025-10-21 19:50         ` Anton Protopopov
2025-10-21 20:17           ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 13/17] libbpf: fix formatting of bpf_object__append_subprog_code Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 14/17] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-10-21 22:18   ` Eduard Zingerman
2025-10-21 22:45     ` Eduard Zingerman
2025-10-24 12:52     ` Anton Protopopov
2025-10-25 17:39       ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 15/17] bpftool: Recognize insn_array map type Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 16/17] selftests/bpf: add new verifier_gotox test Anton Protopopov
2025-10-21 22:42   ` Eduard Zingerman
2025-10-24 11:40     ` Anton Protopopov
2025-10-26 12:34       ` Anton Protopopov
2025-10-27 23:11         ` Eduard Zingerman
2025-10-28 12:06           ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 17/17] selftests/bpf: add C-level selftests for indirect jumps Anton Protopopov
2025-10-22  0:27   ` Eduard Zingerman
2025-10-22 13:34     ` Anton Protopopov
2025-10-25 17:41       ` Anton Protopopov
2025-10-21 18:30 ` [PATCH v6 bpf-next 00/17] BPF " 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=aPfRyNQVP53swJ0l@mail.gmail.com \
    --to=a.s.protopopov@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=aspsk@isovalent.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=qmo@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).