From: John Fastabend <john.fastabend@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: RE: [PATCH bpf-next] selftests/bpf: Using llvm may_goto inline asm for cond_break macro
Date: Mon, 01 Apr 2024 21:29:36 -0700 [thread overview]
Message-ID: <660b89b056220_1a14020831@john.notmuch> (raw)
In-Reply-To: <20240402025446.3215182-1-yonghong.song@linux.dev>
Yonghong Song wrote:
> Currently, cond_break macro uses bytes to encode the may_goto insn.
> Patch [1] in llvm implemented may_goto insn in BPF backend.
> Replace byte-level encoding with llvm inline asm for better usability.
> Using llvm may_goto insn is controlled by macro __BPF_FEATURE_MAY_GOTO.
>
> [1] https://github.com/llvm/llvm-project/commit/0e0bfacff71859d1f9212205f8f873d47029d3fb
>
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> tools/testing/selftests/bpf/bpf_experimental.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/bpf_experimental.h b/tools/testing/selftests/bpf/bpf_experimental.h
> index a5b9df38c162..3329ea080865 100644
> --- a/tools/testing/selftests/bpf/bpf_experimental.h
> +++ b/tools/testing/selftests/bpf/bpf_experimental.h
> @@ -326,6 +326,16 @@ l_true: \
> })
> #endif
>
> +#ifdef __BPF_FEATURE_MAY_GOTO
> +#define cond_break \
> + ({ __label__ l_break, l_continue; \
> + asm volatile goto("may_goto %l[l_break]" \
> + :::: l_break); \
> + goto l_continue; \
> + l_break: break; \
> + l_continue:; \
> + })
> +#else
> #define cond_break \
> ({ __label__ l_break, l_continue; \
> asm volatile goto("1:.byte 0xe5; \
> @@ -337,6 +347,7 @@ l_true: \
> l_break: break; \
> l_continue:; \
> })
> +#endif
>
> #ifndef bpf_nop_mov
> #define bpf_nop_mov(var) \
> --
> 2.43.0
>
>
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2024-04-02 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 2:54 [PATCH bpf-next] selftests/bpf: Using llvm may_goto inline asm for cond_break macro Yonghong Song
2024-04-02 4:29 ` John Fastabend [this message]
2024-04-02 14:20 ` 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=660b89b056220_1a14020831@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@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