BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, x86@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH bpf v3 0/2] bpf, x86: fix per-CPU address resolution into an extended register
Date: Sat, 15 Aug 2026 07:00:10 +0000	[thread overview]
Message-ID: <178677721064.4103653.11399150021505971262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260814220254.3797467-1-vineet.gupta@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:

On Fri, 14 Aug 2026 15:02:52 -0700 you wrote:
> The JIT resolves a per-CPU address with
> 
>   add <dst>, gs:[this_cpu_off]
> 
> but builds the REX prefix with add_1mod(), which sets REX.B. The
> destination is encoded in ModRM.reg, which REX.R extends, and the memory
> operand is disp32 with no base, so REX.B does nothing and the high
> register bit is dropped. Every extended destination therefore resolves
> into whichever register shares the low three bits:
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf, x86: Fix per-CPU address resolution into an extended register
    https://git.kernel.org/bpf/bpf-next/c/5bbbce02e500
  - [bpf,v3,2/2] selftests/bpf: Check per-CPU address resolution per register
    https://git.kernel.org/bpf/bpf-next/c/f61306e8c98c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-15  7:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 22:02 [PATCH bpf v3 0/2] bpf, x86: fix per-CPU address resolution into an extended register Vineet Gupta
2026-08-14 22:02 ` [PATCH bpf v3 1/2] bpf, x86: Fix " Vineet Gupta
2026-08-14 22:02 ` [PATCH bpf v3 2/2] selftests/bpf: Check per-CPU address resolution per register Vineet Gupta
2026-08-14 22:26   ` sashiko-bot
2026-08-14 22:39     ` Vineet Gupta
2026-08-14 22:39   ` bot+bpf-ci
2026-08-14 23:55     ` Vineet Gupta
2026-08-15  1:12       ` Borislav Petkov
2026-08-15  6:59 ` [PATCH bpf v3 0/2] bpf, x86: fix per-CPU address resolution into an extended register Eduard Zingerman
2026-08-15  7:00 ` 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=178677721064.4103653.11399150021505971262.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=stable@vger.kernel.org \
    --cc=vineet.gupta@linux.dev \
    --cc=x86@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