From: Anton Protopopov <a.s.protopopov@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: Yonghong Song <yonghong.song@linux.dev>,
bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Anton Protopopov <aspsk@isovalent.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Quentin Monnet <qmo@kernel.org>
Subject: Re: [RFC bpf-next 8/9] libbpf: support llvm-generated indirect jumps
Date: Mon, 7 Jul 2025 19:34:47 +0000 [thread overview]
Message-ID: <aGwhV6erIeV9Eowg@mail.gmail.com> (raw)
In-Reply-To: <e8a7a143ad1ebb087ff06032068201023aa893f4.camel@gmail.com>
On 25/07/07 12:07PM, Eduard Zingerman wrote:
> On Thu, 2025-07-03 at 11:21 -0700, Eduard Zingerman wrote:
>
> [...]
>
> > > > > .jumptables
> > > > > <subprog-rel-off-0>
> > > > > <subprog-rel-off-1> | <--- jump table #1 symbol:
> > > > > <subprog-rel-off-2> | .size = 2 // number of entries in the jump table
> > > > > ... .value = 1 // offset within .jumptables
> > > > > <subprog-rel-off-N> ^
> > > > > |
> > > > > .text |
> > > > > ... |
> > > > > <insn-N> <------ relocation referencing -'
> > > > > ... jump table #1 symbol
>
> [...]
>
> I think I got it working in:
> https://github.com/eddyz87/llvm-project/tree/separate-jumptables-section
Awesome! I will try to use it tomorrow.
> Changes on top of Yonghong's work.
> An example is in the attachment the gist is:
>
> -------------------------------
>
> $ clang --target=bpf -c -o jump-table-test.o jump-table-test.c
> There are 8 section headers, starting at offset 0xaa0:
>
> Section Headers:
> [Nr] Name Type Address Off Size ES Flg Lk Inf Al
> ...
> [ 4] .jumptables PROGBITS 0000000000000000 000220 000260 00 0 0 1
> ...
>
> Symbol table '.symtab' contains 8 entries:
> Num: Value Size Type Bind Vis Ndx Name
> ...
> 3: 0000000000000000 256 NOTYPE LOCAL DEFAULT 4 .BPF.JT.0.0
> 4: 0000000000000100 352 NOTYPE LOCAL DEFAULT 4 .BPF.JT.0.1
> ...
>
> $ llvm-objdump --no-show-raw-insn -Sdr jump-table-test.o
> jump-table-test.o: file format elf64-bpf
>
> Disassembly of section .text:
>
> 0000000000000000 <foo>:
> ...
> 6: r2 <<= 0x3
> 7: r1 = 0x0 ll
> 0000000000000038: R_BPF_64_64 .jumptables
> 9: r1 += r2
> 10: r1 = *(u64 *)(r1 + 0x0)
> 11: gotox r1
> ...
> 34: r2 <<= 0x3
> 35: r1 = 0x100 ll
> 0000000000000118: R_BPF_64_64 .jumptables
> 37: r1 += r2
> 38: r1 = *(u64 *)(r1 + 0x0)
> 39: gotox r1
> ...
>
> -------------------------------
>
> The changes only touch BPF backend. Can be simplified a bit if I move
> MachineFunction::getJTISymbol to TargetLowering in the shared LLVM
> parts.
> $ cat jump-table-test.c
> struct simple_ctx { int x; };
>
> int bar(int v);
>
> int foo(struct simple_ctx *ctx)
> {
> int ret_user;
>
> switch (ctx->x) {
> case 0:
> ret_user = 2;
> break;
> case 11:
> ret_user = 3;
> break;
> case 27:
> ret_user = 4;
> break;
> case 31:
> ret_user = 5;
> break;
> default:
> ret_user = 19;
> break;
> }
>
> switch (bar(ret_user)) {
> case 1:
> ret_user = 5;
> break;
> case 12:
> ret_user = 7;
> break;
> case 27:
> ret_user = 23;
> break;
> case 32:
> ret_user = 37;
> break;
> case 44:
> ret_user = 77;
> break;
> default:
> ret_user = 11;
> break;
> }
>
> return ret_user;
> }
>
> $ clang --target=bpf -c -o jump-table-test.o jump-table-test.c
> There are 8 section headers, starting at offset 0xaa0:
>
> Section Headers:
> [Nr] Name Type Address Off Size ES Flg Lk Inf Al
> [ 0] NULL 0000000000000000 000000 000000 00 0 0 0
> [ 1] .strtab STRTAB 0000000000000000 000a31 00006b 00 0 0 1
> [ 2] .text PROGBITS 0000000000000000 000040 0001e0 00 AX 0 0 8
> [ 3] .rel.text REL 0000000000000000 000540 000030 10 I 7 2 8
> [ 4] .jumptables PROGBITS 0000000000000000 000220 000260 00 0 0 1
> [ 5] .rel.jumptables REL 0000000000000000 000570 0004c0 10 I 7 4 8
> [ 6] .llvm_addrsig LLVM_ADDRSIG 0000000000000000 000a30 000001 00 E 7 0 1
> [ 7] .symtab SYMTAB 0000000000000000 000480 0000c0 18 1 6 8
> Key to Flags:
> W (write), A (alloc), X (execute), M (merge), S (strings), I (info),
> L (link order), O (extra OS processing required), G (group), T (TLS),
> C (compressed), x (unknown), o (OS specific), E (exclude),
> R (retain), p (processor specific)
>
> Symbol table '.symtab' contains 8 entries:
> Num: Value Size Type Bind Vis Ndx Name
> 0: 0000000000000000 0 NOTYPE LOCAL DEFAULT UND
> 1: 0000000000000000 0 FILE LOCAL DEFAULT ABS jump-table-test.c
> 2: 0000000000000000 0 SECTION LOCAL DEFAULT 2 .text
> 3: 0000000000000000 256 NOTYPE LOCAL DEFAULT 4 .BPF.JT.0.0
> 4: 0000000000000100 352 NOTYPE LOCAL DEFAULT 4 .BPF.JT.0.1
> 5: 0000000000000000 0 SECTION LOCAL DEFAULT 4 .jumptables
> 6: 0000000000000000 480 FUNC GLOBAL DEFAULT 2 foo
> 7: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND bar
>
> $ llvm-objdump --no-show-raw-insn -Sdr jump-table-test.o
> jump-table-test.o: file format elf64-bpf
>
> Disassembly of section .text:
>
> 0000000000000000 <foo>:
> 0: *(u64 *)(r10 - 0x8) = r1
> 1: r1 = *(u64 *)(r10 - 0x8)
> 2: w1 = *(u32 *)(r1 + 0x0)
> 3: *(u64 *)(r10 - 0x18) = r1
> 4: if w1 > 0x1f goto +0x13 <foo+0xc0>
> 5: r2 = *(u64 *)(r10 - 0x18)
> 6: r2 <<= 0x3
> 7: r1 = 0x0 ll
> 0000000000000038: R_BPF_64_64 .jumptables
> 9: r1 += r2
> 10: r1 = *(u64 *)(r1 + 0x0)
> 11: gotox r1
> 12: w1 = 0x2
> 13: *(u32 *)(r10 - 0xc) = w1
> 14: goto +0xc <foo+0xd8>
> 15: w1 = 0x3
> 16: *(u32 *)(r10 - 0xc) = w1
> 17: goto +0x9 <foo+0xd8>
> 18: w1 = 0x4
> 19: *(u32 *)(r10 - 0xc) = w1
> 20: goto +0x6 <foo+0xd8>
> 21: w1 = 0x5
> 22: *(u32 *)(r10 - 0xc) = w1
> 23: goto +0x3 <foo+0xd8>
> 24: w1 = 0x13
> 25: *(u32 *)(r10 - 0xc) = w1
> 26: goto +0x0 <foo+0xd8>
> 27: w1 = *(u32 *)(r10 - 0xc)
> 28: call -0x1
> 00000000000000e0: R_BPF_64_32 bar
> 29: w0 += -0x1
> 30: w1 = w0
> 31: *(u64 *)(r10 - 0x20) = r1
> 32: if w0 > 0x2b goto +0x16 <foo+0x1b8>
> 33: r2 = *(u64 *)(r10 - 0x20)
> 34: r2 <<= 0x3
> 35: r1 = 0x100 ll
> 0000000000000118: R_BPF_64_64 .jumptables
> 37: r1 += r2
> 38: r1 = *(u64 *)(r1 + 0x0)
> 39: gotox r1
> 40: w1 = 0x5
> 41: *(u32 *)(r10 - 0xc) = w1
> 42: goto +0xf <foo+0x1d0>
> 43: w1 = 0x7
> 44: *(u32 *)(r10 - 0xc) = w1
> 45: goto +0xc <foo+0x1d0>
> 46: w1 = 0x17
> 47: *(u32 *)(r10 - 0xc) = w1
> 48: goto +0x9 <foo+0x1d0>
> 49: w1 = 0x25
> 50: *(u32 *)(r10 - 0xc) = w1
> 51: goto +0x6 <foo+0x1d0>
> 52: w1 = 0x4d
> 53: *(u32 *)(r10 - 0xc) = w1
> 54: goto +0x3 <foo+0x1d0>
> 55: w1 = 0xb
> 56: *(u32 *)(r10 - 0xc) = w1
> 57: goto +0x0 <foo+0x1d0>
> 58: w0 = *(u32 *)(r10 - 0xc)
> 59: exit
>
next prev parent reply other threads:[~2025-07-07 19:28 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 8:59 [RFC bpf-next 0/9] BPF indirect jumps Anton Protopopov
2025-06-15 8:59 ` [RFC bpf-next 1/9] bpf: save the start of functions in bpf_prog_aux Anton Protopopov
2025-06-15 8:59 ` [RFC bpf-next 2/9] bpf, x86: add new map type: instructions set Anton Protopopov
2025-06-18 0:57 ` Eduard Zingerman
2025-06-18 2:16 ` Alexei Starovoitov
2025-06-19 18:57 ` Anton Protopopov
2025-06-19 18:55 ` Anton Protopopov
2025-06-19 18:55 ` Eduard Zingerman
2025-06-15 8:59 ` [RFC bpf-next 3/9] selftests/bpf: add selftests for new insn_set map Anton Protopopov
2025-06-18 11:04 ` Eduard Zingerman
2025-06-18 15:16 ` Anton Protopopov
2025-06-15 8:59 ` [RFC bpf-next 4/9] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-06-17 19:41 ` Alexei Starovoitov
2025-06-18 14:28 ` Anton Protopopov
2025-06-15 8:59 ` [RFC bpf-next 5/9] bpf, x86: add support for indirect jumps Anton Protopopov
2025-06-18 3:06 ` Alexei Starovoitov
2025-06-19 19:57 ` Anton Protopopov
2025-06-19 19:58 ` Anton Protopopov
2025-06-18 11:03 ` Eduard Zingerman
2025-06-19 20:13 ` Anton Protopopov
2025-06-15 8:59 ` [RFC bpf-next 6/9] bpf: workaround llvm behaviour with " Anton Protopopov
2025-06-18 11:04 ` Eduard Zingerman
2025-06-18 13:59 ` Alexei Starovoitov
2025-06-15 8:59 ` [RFC bpf-next 7/9] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-06-15 8:59 ` [RFC bpf-next 8/9] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-06-18 3:22 ` Alexei Starovoitov
2025-06-18 15:08 ` Anton Protopopov
2025-07-07 23:45 ` Eduard Zingerman
2025-07-07 23:49 ` Alexei Starovoitov
2025-07-08 0:01 ` Eduard Zingerman
2025-07-08 0:12 ` Alexei Starovoitov
2025-07-08 0:18 ` Eduard Zingerman
2025-07-08 0:49 ` Alexei Starovoitov
2025-07-08 0:51 ` Eduard Zingerman
2025-07-08 20:59 ` Eduard Zingerman
2025-07-08 21:25 ` Alexei Starovoitov
2025-07-08 21:29 ` Eduard Zingerman
2025-07-09 5:33 ` Anton Protopopov
2025-07-09 5:58 ` Eduard Zingerman
2025-07-09 8:38 ` Eduard Zingerman
2025-07-10 5:11 ` Eduard Zingerman
2025-07-10 6:10 ` Anton Protopopov
2025-07-10 6:13 ` Eduard Zingerman
2025-06-18 19:49 ` Eduard Zingerman
2025-06-27 2:28 ` Eduard Zingerman
2025-06-27 10:18 ` Anton Protopopov
2025-07-03 18:21 ` Eduard Zingerman
2025-07-03 19:03 ` Anton Protopopov
2025-07-07 19:07 ` Eduard Zingerman
2025-07-07 19:34 ` Anton Protopopov [this message]
2025-07-07 21:44 ` Yonghong Song
2025-07-08 5:58 ` Yonghong Song
2025-07-08 8:30 ` Eduard Zingerman
2025-07-08 10:42 ` Eduard Zingerman
2025-06-15 8:59 ` [RFC bpf-next 9/9] selftests/bpf: add selftests for " Anton Protopopov
2025-06-18 3:24 ` Alexei Starovoitov
2025-06-18 14:49 ` Anton Protopopov
2025-06-18 16:01 ` Alexei Starovoitov
2025-06-18 16:36 ` Anton Protopopov
2025-06-18 16:43 ` Alexei Starovoitov
2025-06-18 20:25 ` Anton Protopopov
2025-06-18 21:59 ` Alexei Starovoitov
2025-06-19 5:05 ` Anton Protopopov
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=aGwhV6erIeV9Eowg@mail.gmail.com \
--to=a.s.protopopov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.