Commit d00d5b82 authored by Dave Thaler's avatar Dave Thaler Committed by Alexei Starovoitov

bpf, docs: Add note about type convention

Add explanation about use of "u64", "u32", etc. as
the type convention used in BPF documentation.
Signed-off-by: default avatarDave Thaler <dthaler@microsoft.com>
Acked-by: default avatarDavid Vernet <void@manifault.com>
Link: https://lore.kernel.org/r/20230127014706.1005-1-dthaler1968@googlemail.comSigned-off-by: default avatarAlexei Starovoitov <ast@kernel.org>
parent 27b53b73
...@@ -7,6 +7,11 @@ eBPF Instruction Set Specification, v1.0 ...@@ -7,6 +7,11 @@ eBPF Instruction Set Specification, v1.0
This document specifies version 1.0 of the eBPF instruction set. This document specifies version 1.0 of the eBPF instruction set.
Documentation conventions
=========================
For brevity, this document uses the type notion "u64", "u32", etc.
to mean an unsigned integer whose width is the specified number of bits.
Registers and calling convention Registers and calling convention
================================ ================================
...@@ -164,6 +169,8 @@ the destination register is unchanged whereas for ``BPF_ALU`` the upper ...@@ -164,6 +169,8 @@ the destination register is unchanged whereas for ``BPF_ALU`` the upper
dst = (u32) ((u32) dst + (u32) src) dst = (u32) ((u32) dst + (u32) src)
where '(u32)' indicates that the upper 32 bits are zeroed.
``BPF_ADD | BPF_X | BPF_ALU64`` means:: ``BPF_ADD | BPF_X | BPF_ALU64`` means::
dst = dst + src dst = dst + src
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment