lkml.org 
[lkml]   [2023]   [Oct]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH bpf 0/2] riscv, bpf: Properly sign-extend return values
From
Date
Hello:

This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 4 Oct 2023 14:07:04 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> The RISC-V architecture does not expose sub-registers, and hold all
> 32-bit values in a sign-extended format [1] [2]:
>
> | The compiler and calling convention maintain an invariant that all
> | 32-bit values are held in a sign-extended format in 64-bit
> | registers. Even 32-bit unsigned integers extend bit 31 into bits
> | 63 through 32. Consequently, conversion between unsigned and
> | signed 32-bit integers is a no-op, as is conversion from a signed
> | 32-bit integer to a signed 64-bit integer.
>
> [...]

Here is the summary with links:
- [bpf,1/2] riscv, bpf: Sign-extend return values
https://git.kernel.org/bpf/bpf/c/2f1b0d3d7331
- [bpf,2/2] riscv, bpf: Track both a0 (RISC-V ABI) and a5 (BPF) return values
https://git.kernel.org/bpf/bpf/c/7112cd26e606

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


\
 
 \ /
  Last update: 2023-10-09 15:31    [W:0.100 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site