From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH] selftests/bpf: Fix chained_global_func_calls_success() for cpu v4
Date: Thu, 13 Aug 2026 16:32:54 +0000 [thread overview]
Message-ID: <178663877455.2948096.7160178725216923389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813150641.3347662-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 13 Aug 2026 08:06:41 -0700 you wrote:
> The chained_global_func_calls_success() test hardcodes the instruction
> counts reported by the verifier's per-subprog stats:
>
> subprog {{[0-9]+}} (global_good) global insns_self 5 insns_total 5 stack
> processed 14 insns
>
> global_good() does 'return arr[0]', where arr[] is an int array and the
> return type is long. Without cpu v4 this is a zero-extending load
> followed by a <<32/s>>32 sign-extension pair. With -mcpu=v4 llvm emits a
> single sign-extending load instead:
>
> [...]
Here is the summary with links:
- selftests/bpf: Fix chained_global_func_calls_success() for cpu v4
https://git.kernel.org/bpf/bpf-next/c/9786d424a36b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-13 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:06 [PATCH] selftests/bpf: Fix chained_global_func_calls_success() for cpu v4 Yonghong Song
2026-08-13 16:32 ` patchwork-bot+netdevbpf [this message]
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=178663877455.2948096.7160178725216923389.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--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.