All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: alexei.starovoitov@gmail.com, memxor@gmail.com,
	bpf@vger.kernel.org, iii@linux.ibm.com
Subject: Re: [PATCH bpf-next v2 1/3] bpf, s390: Mask the count of 32-bit shifts by register
Date: Fri, 16 Oct 2026 17:50:19 +0000	[thread overview]
Message-ID: <179217301901.897417.16584914717846246156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016101822.632891-1-daniel@iogearbox.net>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 16 Oct 2026 12:18:20 +0200 you wrote:
> RFC9669 defines the shifts as dst <<= (src & mask), dst >>= (src & mask)
> and sign extending dst >>= (src & mask), where "shift operations use a mask
> of 0x3F (63) for 64-bit operations and 0x1F (31) for 32-bit operations"
> (Section 4.1), which the interpreter implements. On x86-64 and arm64 the
> hardware does so by itself, so both JITs emit the shift alone and conform.
> 
> The 32-bit shifts by register of the s390x JIT do not conform to the spec.
> They emit sll, srl and sra with the count in the address of the second
> operand, of which the "rightmost six bits indicate the number of bit
> positions to be shifted" (z/Architecture Principles of Operation,
> SA22-7832-13), so a count of 32 to 63 clears the register, or fills it
> with the sign for sra, instead of shifting by the count masked with 31.
> The 64-bit sllg, srlg and srag take six bits as well, which is the mask
> there, so only the 32-bit forms differ.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/3] bpf, s390: Mask the count of 32-bit shifts by register
    https://git.kernel.org/bpf/bpf-next/c/4d8c247f1a21
  - [bpf-next,v2,2/3] selftests/bpf: Restore the je <-> jmp distance in convergence check
    https://git.kernel.org/bpf/bpf-next/c/b5fc954c39d4
  - [bpf-next,v2,3/3] selftests/bpf: Follow-up to JIT instruction tests
    https://git.kernel.org/bpf/bpf-next/c/b4e14f47371c

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-10-16 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 10:18 [PATCH bpf-next v2 1/3] bpf, s390: Mask the count of 32-bit shifts by register Daniel Borkmann
2026-10-16 10:18 ` [PATCH bpf-next v2 2/3] selftests/bpf: Restore the je <-> jmp distance in convergence check Daniel Borkmann
2026-10-16 10:18 ` [PATCH bpf-next v2 3/3] selftests/bpf: Follow-up to JIT instruction tests Daniel Borkmann
2026-10-16 10:58   ` bot+bpf-ci
2026-10-16 11:33     ` Daniel Borkmann
2026-10-16 17:50 ` 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=179217301901.897417.16584914717846246156.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=iii@linux.ibm.com \
    --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 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.