From: Eduard Zingerman <eddyz87@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, bpf@vger.kernel.org
Cc: daniel@iogearbox.net, andrii@kernel.org, martin.lau@kernel.org,
memxor@gmail.com, john.fastabend@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH v6 bpf-next 3/4] bpf: Add cond_break macro
Date: Wed, 06 Mar 2024 15:26:45 +0200 [thread overview]
Message-ID: <e4fcd2c9f88e7ce31d356cb31e686bab22382bab.camel@gmail.com> (raw)
In-Reply-To: <20240306031929.42666-4-alexei.starovoitov@gmail.com>
On Tue, 2024-03-05 at 19:19 -0800, Alexei Starovoitov wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Use may_goto instruction to implement cond_break macro.
> Ideally the macro should be written as:
> asm volatile goto(".byte 0xe5;
> .byte 0;
> .short %l[l_break] ...
> .long 0;
> but LLVM doesn't recognize fixup of 2 byte PC relative yet.
> Hence use
> asm volatile goto(".byte 0xe5;
> .byte 0;
> .long %l[l_break] ...
> .short 0;
> that produces correct asm on little endian.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
I tried rewriting with offset +1 and an additional goto:
({ __label__ l_break, l_continue; \
asm volatile goto("%[jcond]; goto %l[l_break];"\
:: __imm_insn(jcond, BPF_RAW_INSN(BPF_JMP | BPF_JCOND, 0, 0, 1, 0)) \
:: l_break); \
goto l_continue; \
l_break: break; \
l_continue:; \
})
But BPF_RAW_INSN needs filter.h, which can't be included because of vmlinux.h,
unfortunate :(
next prev parent reply other threads:[~2024-03-06 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 3:19 [PATCH v6 bpf-next 0/4] bpf: Introduce may_goto and cond_break Alexei Starovoitov
2024-03-06 3:19 ` [PATCH v6 bpf-next 1/4] bpf: Introduce may_goto instruction Alexei Starovoitov
2024-03-06 13:12 ` Eduard Zingerman
2024-03-06 16:40 ` Alexei Starovoitov
2024-03-06 18:33 ` Andrii Nakryiko
2024-03-06 18:38 ` Alexei Starovoitov
2024-03-06 3:19 ` [PATCH v6 bpf-next 2/4] bpf: Recognize that two registers are safe when their ranges match Alexei Starovoitov
2024-03-06 13:07 ` Eduard Zingerman
2024-03-06 3:19 ` [PATCH v6 bpf-next 3/4] bpf: Add cond_break macro Alexei Starovoitov
2024-03-06 13:26 ` Eduard Zingerman [this message]
2024-03-06 16:51 ` Alexei Starovoitov
2024-03-06 3:19 ` [PATCH v6 bpf-next 4/4] selftests/bpf: Test may_goto Alexei Starovoitov
2024-03-06 18:50 ` [PATCH v6 bpf-next 0/4] bpf: Introduce may_goto and cond_break patchwork-bot+netdevbpf
2024-03-06 19:15 ` John Fastabend
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=e4fcd2c9f88e7ce31d356cb31e686bab22382bab.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.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