From: Eduard Zingerman <eddyz87@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 v2 1/2] bpf: Get better reg range with ldsx and 32bit compare
Date: Fri, 12 Jul 2024 13:49:09 -0700 [thread overview]
Message-ID: <e05bd24690aab17ec0764e6318d13bf5690f6bdd.camel@gmail.com> (raw)
In-Reply-To: <20240712202815.3540564-1-yonghong.song@linux.dev>
On Fri, 2024-07-12 at 13:28 -0700, Yonghong Song wrote:
[...]
> +
> + /* Here we would like to handle a special case after sign extending load,
> + * when upper bits for a 64-bit range are all 1s or all 0s.
> + *
> + * Upper bits are all 1s when register is in a rage:
> + * [0xffff_ffff_0000_0000, 0xffff_ffff_ffff_ffff]
> + * Upper bits are all 0s when register is in a range:
> + * [0x0000_0000_0000_0000, 0x0000_0000_ffff_ffff]
> + * Together this forms are continuous range:
> + * [0xffff_ffff_0000_0000, 0x0000_0000_ffff_ffff]
> + *
> + * Now, suppose that register range is in fact tighter:
> + * [0xffff_ffff_8000_0000, 0x0000_0000_ffff_ffff] (R)
> + * Also suppose that it's 32-bit range is positive,
> + * meaning that lower 32-bits of the full 64-bit register
> + * are in the range:
> + * [0x0000_0000, 0x7fff_ffff] (W)
> + *
> + * It this happens, then any value in a range:
> + * [0xffff_ffff_0000_0000, 0xffff_ffff_7fff_ffff]
> + * is smaller than a lowest bound of the range (R):
> + * 0xffff_ffff_8000_0000
> + * which means that upper bits of the full 64-bit register
> + * can't be all 1s, when lower bits are in range (W).
> + *
> + * Note that:
> + * - 0xffff_ffff_8000_0000 == (s64)S32_MIN
> + * - 0x0000_0000_ffff_ffff == (s64)S32_MAX
> + * These relations are used in the conditions below.
> + */
> + if (reg->s32_min_value >= 0) {
> + if ((reg->smin_value >= S32_MIN && reg->smax_value <= S32_MAX) ||
> + (reg->smin_value >= S16_MIN && reg->smax_value <= S16_MAX) ||
> + (reg->smin_value >= S8_MIN && reg->smax_value <= S8_MAX)) {
Sorry, maybe there is still something I don't understand.
Why do we need 3 different checks here?
- S32_MIN <= r <= S32_MAX (R32)
- S16_MIN <= r <= S16_MAX (R16)
- S8_MIN <= r <= S8_MAX (R8)
If R8 or R16 is true then R32 is true, so it seems this condition is redundant.
> + reg->smin_value = reg->umin_value = reg->s32_min_value;
> + reg->smax_value = reg->umax_value = reg->s32_max_value;
> + reg->var_off = tnum_intersect(reg->var_off,
> + tnum_range(reg->smin_value,
> + reg->smax_value));
> + }
> + }
[...]
next prev parent reply other threads:[~2024-07-12 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 20:28 [PATCH bpf-next v2 1/2] bpf: Get better reg range with ldsx and 32bit compare Yonghong Song
2024-07-12 20:28 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add ldsx selftests for ldsx and subreg compare Yonghong Song
2024-07-12 20:30 ` [PATCH bpf-next v2 1/2] bpf: Get better reg range with ldsx and 32bit compare Alexei Starovoitov
2024-07-12 21:24 ` Yonghong Song
2024-07-12 20:49 ` Eduard Zingerman [this message]
2024-07-12 21:29 ` Yonghong Song
2024-07-12 20:50 ` Eduard Zingerman
2024-07-12 21:30 ` Yonghong Song
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=e05bd24690aab17ec0764e6318d13bf5690f6bdd.camel@gmail.com \
--to=eddyz87@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