From: John Fastabend <john.fastabend@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 bpf-next 2/2] bpf: inline bpf_get_branch_snapshot() helper
Date: Wed, 03 Apr 2024 15:10:09 -0700 [thread overview]
Message-ID: <660dd3c19a5c9_2144820828@john.notmuch> (raw)
In-Reply-To: <CAEf4BzZ_6hzWoniF+6jb6cOXK48EHNMH0ziZ1o26KW+Zo7OKyQ@mail.gmail.com>
Andrii Nakryiko wrote:
> On Tue, Apr 2, 2024 at 12:05 PM Andrii Nakryiko <andrii@kernel.org> wrote:
> >
> > Inline bpf_get_branch_snapshot() helper using architecture-agnostic
> > inline BPF code which calls directly into underlying callback of
> > perf_snapshot_branch_stack static call. This callback is set early
> > during kernel initialization and is never updated or reset, so it's ok
> > to fetch actual implementation using static_call_query() and call
> > directly into it.
> >
> > This change eliminates a full function call and saves one LBR entry
> > in PERF_SAMPLE_BRANCH_ANY LBR mode.
> >
> > Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> > ---
> > kernel/bpf/verifier.c | 55 +++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 55 insertions(+)
> >
> > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> > index fcb62300f407..49789da56f4b 100644
> > --- a/kernel/bpf/verifier.c
> > +++ b/kernel/bpf/verifier.c
> > @@ -20157,6 +20157,61 @@ static int do_misc_fixups(struct bpf_verifier_env *env)
> > goto next_insn;
> > }
> >
> > + /* Implement bpf_get_branch_snapshot inline. */
> > + if (prog->jit_requested && BITS_PER_LONG == 64 &&
> > + insn->imm == BPF_FUNC_get_branch_snapshot) {
> > + /* We are dealing with the following func protos:
> > + * u64 bpf_get_branch_snapshot(void *buf, u32 size, u64 flags);
> > + * int perf_snapshot_branch_stack(struct perf_branch_entry *entries, u32 cnt);
> > + */
> > + const u32 br_entry_size = sizeof(struct perf_branch_entry);
> > +
> > + /* struct perf_branch_entry is part of UAPI and is
> > + * used as an array element, so extremely unlikely to
> > + * ever grow or shrink
> > + */
> > + BUILD_BUG_ON(br_entry_size != 24);
> > +
> > + /* if (unlikely(flags)) return -EINVAL */
> > + insn_buf[0] = BPF_JMP_IMM(BPF_JNE, BPF_REG_3, 0, 7);
> > +
> > + /* Transform size (bytes) into number of entries (cnt = size / 24).
> > + * But to avoid expensive division instruction, we implement
> > + * divide-by-3 through multiplication, followed by further
> > + * division by 8 through 3-bit right shift.
> > + * Refer to book "Hacker's Delight, 2nd ed." by Henry S. Warren, Jr.,
> > + * p. 227, chapter "Unsigned Divison by 3" for details and proofs.
> > + *
> > + * N / 3 <=> M * N / 2^33, where M = (2^33 + 1) / 3 = 0xaaaaaaab.
> > + */
Nice bit of magic. Thanks for the reference.
> > + insn_buf[1] = BPF_MOV32_IMM(BPF_REG_0, 0xaaaaaaab);
> > + insn_buf[2] = BPF_ALU64_REG(BPF_REG_2, BPF_REG_0, 0);
>
> Doh, this should be:
>
> insn_buf[2] = BPF_ALU64_REG(BPF_MUL, BPF_REG_2, BPF_REG_0);
>
> I'll wait a bit for any other feedback, will retest everything on real
> hardware again, and will submit v2 tomorrow.
>
> pw-bot: cr
>
LGTM. With above fix,
Acked-by: John Fastabend <john.fastabend@gmail.com>
>
> > + insn_buf[3] = BPF_ALU64_IMM(BPF_RSH, BPF_REG_2, 36);
> > +
> > + /* call perf_snapshot_branch_stack implementation */
> > + insn_buf[4] = BPF_EMIT_CALL(static_call_query(perf_snapshot_branch_stack));
> > + /* if (entry_cnt == 0) return -ENOENT */
> > + insn_buf[5] = BPF_JMP_IMM(BPF_JEQ, BPF_REG_0, 0, 4);
> > + /* return entry_cnt * sizeof(struct perf_branch_entry) */
> > + insn_buf[6] = BPF_ALU32_IMM(BPF_MUL, BPF_REG_0, br_entry_size);
> > + insn_buf[7] = BPF_JMP_A(3);
> > + /* return -EINVAL; */
> > + insn_buf[8] = BPF_MOV64_IMM(BPF_REG_0, -EINVAL);
> > + insn_buf[9] = BPF_JMP_A(1);
> > + /* return -ENOENT; */
> > + insn_buf[10] = BPF_MOV64_IMM(BPF_REG_0, -ENOENT);
> > + cnt = 11;
> > +
> > + new_prog = bpf_patch_insn_data(env, i + delta, insn_buf, cnt);
> > + if (!new_prog)
> > + return -ENOMEM;
> > +
> > + delta += cnt - 1;
> > + env->prog = prog = new_prog;
> > + insn = new_prog->insnsi + i + delta;
> > + continue;
> > + }
> > +
> > /* Implement bpf_kptr_xchg inline */
> > if (prog->jit_requested && BITS_PER_LONG == 64 &&
> > insn->imm == BPF_FUNC_kptr_xchg &&
> > --
> > 2.43.0
> >
>
next prev parent reply other threads:[~2024-04-03 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:05 [PATCH v2 bpf-next 0/2] Inline bpf_get_branch_snapshot() BPF helper Andrii Nakryiko
2024-04-02 19:05 ` [PATCH v2 bpf-next 1/2] bpf: make bpf_get_branch_snapshot() architecture-agnostic Andrii Nakryiko
2024-04-02 19:05 ` [PATCH v2 bpf-next 2/2] bpf: inline bpf_get_branch_snapshot() helper Andrii Nakryiko
2024-04-02 23:22 ` Andrii Nakryiko
2024-04-03 22:10 ` John Fastabend [this message]
2024-04-03 17:51 ` Alexei Starovoitov
2024-04-03 18:09 ` Andrii Nakryiko
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=660dd3c19a5c9_2144820828@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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