diff options
author | Dave Thaler <dthaler1968@googlemail.com> | 2024-05-20 14:52:55 -0700 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2024-05-25 10:39:03 -0700 |
commit | 4e1215d9a1903fc9e976aa8903674d050c7af5ff (patch) | |
tree | c087489b3a7f5ffb2b73a42022a4a4ad796c70ba /net/ipv4/tcp_output.c | |
parent | a985fdca5e7e665d58dc40c92a67c8b67b6291db (diff) | |
download | linux-4e1215d9a1903fc9e976aa8903674d050c7af5ff.tar.gz linux-4e1215d9a1903fc9e976aa8903674d050c7af5ff.tar.bz2 linux-4e1215d9a1903fc9e976aa8903674d050c7af5ff.zip |
bpf, docs: clarify sign extension of 64-bit use of 32-bit imm
imm is defined as a 32-bit signed integer.
{MOV, K, ALU64} says it does "dst = src" (where src is 'imm') and it
does do dst = (s64)imm, which in that sense does sign extend imm. The MOVSX
instruction is explained as sign extending, so added the example of
{MOV, K, ALU64} to make this more clear.
{JLE, K, JMP} says it does "PC += offset if dst <= src" (where src is 'imm',
and the comparison is unsigned). This was apparently ambiguous to some
readers as to whether the comparison was "dst <= (u64)(u32)imm" or
"dst <= (u64)(s64)imm" so added an example to make this more clear.
v1 -> v2: Address comments from Yonghong
Signed-off-by: Dave Thaler <dthaler1968@googlemail.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
Acked-by: David Vernet <void@manifault.com>
Link: https://lore.kernel.org/r/20240520215255.10595-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'net/ipv4/tcp_output.c')
0 files changed, 0 insertions, 0 deletions