<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/Documentation/bpf/standardization, branch v6.12.80</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v6.12.80</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v6.12.80'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2024-06-23T16:10:26+00:00</updated>
<entry>
<title>bpf, docs: Address comments from IETF Area Directors</title>
<updated>2024-06-23T16:10:26+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-06-23T15:04:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=04efaebd72d1d3d9991841051fafc6b195f3676d'/>
<id>urn:sha1:04efaebd72d1d3d9991841051fafc6b195f3676d</id>
<content type='text'>
This patch does the following to address IETF feedback:

* Remove mention of "program type" and reference future
  docs (and mention platform-specific docs exist) for
  helper functions and BTF. Addresses Roman Danyliw's
  comments based on GENART review from Ines Robles [0].

* Add reference for endianness as requested by John
  Scudder [1].

* Added bit numbers to top of 32-bit wide format diagrams
  as requested by Paul Wouters [2].

* Added more text about why BPF doesn't stand for anything, based
  on text from ebpf.io [3], as requested by Eric Vyncke and
  Gunter Van de Velde [4].

* Replaced "htobe16" (and similar) and the direction-specific
  description with just "be16" (and similar) and a direction-agnostic
  description, to match the direction-agnostic description in
  the Byteswap Instructions section. Based on feedback from Eric
  Vyncke [5].

[0] https://mailarchive.ietf.org/arch/msg/bpf/DvDgDWOiwk05OyNlWlAmELZFPlM/

[1] https://mailarchive.ietf.org/arch/msg/bpf/eKNXpU4jCLjsbZDSw8LjI29M3tM/

[2] https://mailarchive.ietf.org/arch/msg/bpf/hGk8HkYxeZTpdu9qW_MvbGKj7WU/

[3] https://ebpf.io/what-is-ebpf/#what-do-ebpf-and-bpf-stand-for

[4] https://mailarchive.ietf.org/arch/msg/bpf/i93lzdN3ewnzzS_JMbinCIYxAIU/

[5] https://mailarchive.ietf.org/arch/msg/bpf/KBWXbMeDcSrq4vsKR_KkBbV6hI4/

Acked-by: David Vernet &lt;void@manifault.com&gt;
Signed-off-by: Dave Thaler &lt;dthaler1968@googlemail.com&gt;
Link: https://lore.kernel.org/r/20240623150453.10613-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Fix instruction.rst indentation</title>
<updated>2024-05-26T16:58:42+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-05-26T06:18:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=e245ef8a0b06fa5a18ca3bdcf82430166419283e'/>
<id>urn:sha1:e245ef8a0b06fa5a18ca3bdcf82430166419283e</id>
<content type='text'>
The table captions patch corrected indented most tables to work with
the table directive for adding a caption but missed two of them.

Signed-off-by: Dave Thaler &lt;dthaler1968@gmail.com&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
Link: https://lore.kernel.org/r/20240526061815.22497-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Clarify call local offset</title>
<updated>2024-05-25T17:41:57+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-05-25T15:33:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f980f13e4eb299abba6692365315196e1ba6fd2c'/>
<id>urn:sha1:f980f13e4eb299abba6692365315196e1ba6fd2c</id>
<content type='text'>
In the Jump instructions section it explains that the offset is
"relative to the instruction following the jump instruction".
But the program-local section confusingly said "referenced by
offset from the call instruction, similar to JA".

This patch updates that sentence with consistent wording, saying
it's relative to the instruction following the call instruction.

Signed-off-by: Dave Thaler &lt;dthaler1968@gmail.com&gt;
Acked-by: Yonghong Song &lt;yonghong.song@linux.dev&gt;
Link: https://lore.kernel.org/r/20240525153332.21355-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Add table captions</title>
<updated>2024-05-25T17:39:31+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-05-24T16:46:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=6a6d8b6f00ade597e0030669fae3fdf57cfba33b'/>
<id>urn:sha1:6a6d8b6f00ade597e0030669fae3fdf57cfba33b</id>
<content type='text'>
As suggested by Ines Robles in his IETF GENART review at
https://datatracker.ietf.org/doc/review-ietf-bpf-isa-02-genart-lc-robles-2024-05-16/

Signed-off-by: Dave Thaler &lt;dthaler1968@gmail.com&gt;
Link: https://lore.kernel.org/r/20240524164618.18894-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: clarify sign extension of 64-bit use of 32-bit imm</title>
<updated>2024-05-25T17:39:03+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-05-20T21:52:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4e1215d9a1903fc9e976aa8903674d050c7af5ff'/>
<id>urn:sha1:4e1215d9a1903fc9e976aa8903674d050c7af5ff</id>
<content type='text'>
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 &lt;= src" (where src is 'imm',
and the comparison is unsigned). This was apparently ambiguous to some
readers as to whether the comparison was "dst &lt;= (u64)(u32)imm" or
"dst &lt;= (u64)(s64)imm" so added an example to make this more clear.

v1 -&gt; v2: Address comments from Yonghong

Signed-off-by: Dave Thaler &lt;dthaler1968@googlemail.com&gt;
Acked-by: Yonghong Song &lt;yonghong.song@linux.dev&gt;
Acked-by: David Vernet &lt;void@manifault.com&gt;
Link: https://lore.kernel.org/r/20240520215255.10595-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Use RFC 2119 language for ISA requirements</title>
<updated>2024-05-25T17:38:35+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-05-17T16:58:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=a985fdca5e7e665d58dc40c92a67c8b67b6291db'/>
<id>urn:sha1:a985fdca5e7e665d58dc40c92a67c8b67b6291db</id>
<content type='text'>
Per IETF convention and discussion at LSF/MM/BPF, use MUST etc.
keywords as requested by IETF Area Director review.  Also as
requested, indicate that documenting BTF is out of scope of this
document and will be covered by a separate IETF specification.

Added paragraph about the terminology that is required IETF boilerplate
and must be worded exactly as such.

Signed-off-by: Dave Thaler &lt;dthaler1968@googlemail.com&gt;
Acked-by: David Vernet &lt;void@manifault.com&gt;
Link: https://lore.kernel.org/r/20240517165855.4688-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Move sentence about returning R0 to abi.rst</title>
<updated>2024-05-25T17:37:49+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-05-17T15:34:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4652072e7b9d643edc9ebb04e3e2c021461b7af0'/>
<id>urn:sha1:4652072e7b9d643edc9ebb04e3e2c021461b7af0</id>
<content type='text'>
As discussed at LSF/MM/BPF, the sentence about using R0 for returning
values from calls is part of the calling convention and belongs in
abi.rst.  Any further additions or clarifications to this text are left
for future patches on abi.rst.  The current patch is simply to unblock
progression of instruction-set.rst to a standard.

In contrast, the restriction of register numbers to the range 0-10
is untouched, left in the instruction-set.rst definition of the
src_reg and dst_reg fields.

Signed-off-by: Dave Thaler &lt;dthaler1968@googlemail.com&gt;
Link: https://lore.kernel.org/r/20240517153445.3914-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Fix the description of 'src' in ALU instructions</title>
<updated>2024-05-15T16:34:54+00:00</updated>
<author>
<name>Puranjay Mohan</name>
<email>puranjay@kernel.org</email>
</author>
<published>2024-05-14T13:03:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7a8030057f6791d35dd20987f9ff15855c01c1bb'/>
<id>urn:sha1:7a8030057f6791d35dd20987f9ff15855c01c1bb</id>
<content type='text'>
An ALU instruction's source operand can be the value in the source
register or the 32-bit immediate value encoded in the instruction. This
is controlled by the 's' bit of the 'opcode'.

The current description explicitly uses the phrase 'value of the source
register' when defining the meaning of 'src'.

Change the description to use 'source operand' in place of 'value of the
source register'.

Signed-off-by: Puranjay Mohan &lt;puranjay@kernel.org&gt;
Acked-by: Dave Thaler &lt;dthaler1968@gmail.com&gt;
Link: https://lore.kernel.org/r/20240514130303.113607-1-puranjay@kernel.org
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
<entry>
<title>bpf, docs: Clarify PC use in instruction-set.rst</title>
<updated>2024-04-29T09:54:42+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-04-26T23:11:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=07801a24e2f18624cd2400ce15f14569eb416c9a'/>
<id>urn:sha1:07801a24e2f18624cd2400ce15f14569eb416c9a</id>
<content type='text'>
This patch elaborates on the use of PC by expanding the PC acronym,
explaining the units, and the relative position to which the offset
applies.

Signed-off-by: Dave Thaler &lt;dthaler1968@googlemail.com&gt;
Signed-off-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Reviewed-by: David Vernet &lt;void@manifault.com&gt;
Link: https://lore.kernel.org/bpf/20240426231126.5130-1-dthaler1968@gmail.com
</content>
</entry>
<entry>
<title>bpf, docs: Add introduction for use in the ISA Internet Draft</title>
<updated>2024-04-26T02:15:21+00:00</updated>
<author>
<name>Dave Thaler</name>
<email>dthaler1968@googlemail.com</email>
</author>
<published>2024-04-22T19:09:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=e51b907d40329d4b4517a155e0bc0bf593d6767d'/>
<id>urn:sha1:e51b907d40329d4b4517a155e0bc0bf593d6767d</id>
<content type='text'>
The proposed intro paragraph text is derived from the first paragraph
of the IETF BPF WG charter at https://datatracker.ietf.org/wg/bpf/about/

Signed-off-by: Dave Thaler &lt;dthaler1968@gmail.com&gt;
Acked-by: David Vernet &lt;void@manifault.com&gt;
Link: https://lore.kernel.org/r/20240422190942.24658-1-dthaler1968@gmail.com
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
</content>
</entry>
</feed>
