* [PATCH bpf-next] Introduce concept of conformance groups
@ 2024-01-08 21:42 Dave Thaler
2024-01-08 21:42 ` [Bpf] " Dave Thaler
` (3 more replies)
0 siblings, 4 replies; 7+ messages in thread
From: Dave Thaler @ 2024-01-08 21:42 UTC (permalink / raw)
To: bpf; +Cc: bpf, Dave Thaler
The discussion of what the actual conformance groups should be
is still in progress, so this is just part 1 which only uses
"legacy" for deprecated instructions and "basic" for everything
else. Subsequent patches will add more groups as discussion
continues.
Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
---
.../bpf/standardization/instruction-set.rst | 26 ++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
index 245b6defc..eb0f234a8 100644
--- a/Documentation/bpf/standardization/instruction-set.rst
+++ b/Documentation/bpf/standardization/instruction-set.rst
@@ -97,6 +97,28 @@ Definitions
A: 10000110
B: 11111111 10000110
+Conformance groups
+------------------
+
+An implementation does not need to support all instructions specified in this
+document (e.g., deprecated instructions). Instead, a number of conformance
+groups are specified. An implementation must support the "basic" conformance
+group and may support additional conformance groups, where supporting a
+conformance group means it must support all instructions in that conformance
+group.
+
+The use of named conformance groups enables interoperability between a runtime
+that executes instructions, and tools as such compilers that generate
+instructions for the runtime. Thus, capability discovery in terms of
+conformance groups might be done manually by users or automatically by tools.
+
+Each conformance group has a short ASCII label (e.g., "basic") that
+corresponds to a set of instructions that are mandatory. That is, each
+instruction has one or more conformance groups of which it is a member.
+
+The "basic" conformance group includes all instructions defined in this
+specification unless otherwise noted.
+
Instruction encoding
====================
@@ -610,4 +632,6 @@ Legacy BPF Packet access instructions
BPF previously introduced special instructions for access to packet data that were
carried over from classic BPF. However, these instructions are
-deprecated and should no longer be used.
+deprecated and should no longer be used. All legacy packet access
+instructions belong to the "legacy" conformance group instead of the "basic"
+conformance group.
--
2.40.1
^ permalink raw reply related [flat|nested] 7+ messages in thread
* [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
2024-01-08 21:42 [PATCH bpf-next] Introduce concept of conformance groups Dave Thaler
@ 2024-01-08 21:42 ` Dave Thaler
2024-01-09 2:16 ` Alexei Starovoitov
` (2 subsequent siblings)
3 siblings, 0 replies; 7+ messages in thread
From: Dave Thaler @ 2024-01-08 21:42 UTC (permalink / raw)
To: bpf; +Cc: bpf, Dave Thaler
The discussion of what the actual conformance groups should be
is still in progress, so this is just part 1 which only uses
"legacy" for deprecated instructions and "basic" for everything
else. Subsequent patches will add more groups as discussion
continues.
Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
---
.../bpf/standardization/instruction-set.rst | 26 ++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
index 245b6defc..eb0f234a8 100644
--- a/Documentation/bpf/standardization/instruction-set.rst
+++ b/Documentation/bpf/standardization/instruction-set.rst
@@ -97,6 +97,28 @@ Definitions
A: 10000110
B: 11111111 10000110
+Conformance groups
+------------------
+
+An implementation does not need to support all instructions specified in this
+document (e.g., deprecated instructions). Instead, a number of conformance
+groups are specified. An implementation must support the "basic" conformance
+group and may support additional conformance groups, where supporting a
+conformance group means it must support all instructions in that conformance
+group.
+
+The use of named conformance groups enables interoperability between a runtime
+that executes instructions, and tools as such compilers that generate
+instructions for the runtime. Thus, capability discovery in terms of
+conformance groups might be done manually by users or automatically by tools.
+
+Each conformance group has a short ASCII label (e.g., "basic") that
+corresponds to a set of instructions that are mandatory. That is, each
+instruction has one or more conformance groups of which it is a member.
+
+The "basic" conformance group includes all instructions defined in this
+specification unless otherwise noted.
+
Instruction encoding
====================
@@ -610,4 +632,6 @@ Legacy BPF Packet access instructions
BPF previously introduced special instructions for access to packet data that were
carried over from classic BPF. However, these instructions are
-deprecated and should no longer be used.
+deprecated and should no longer be used. All legacy packet access
+instructions belong to the "legacy" conformance group instead of the "basic"
+conformance group.
--
2.40.1
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
2024-01-08 21:42 [PATCH bpf-next] Introduce concept of conformance groups Dave Thaler
2024-01-08 21:42 ` [Bpf] " Dave Thaler
@ 2024-01-09 2:16 ` Alexei Starovoitov
2024-01-09 2:16 ` Alexei Starovoitov
2024-01-09 16:10 ` David Vernet
2024-01-12 2:40 ` patchwork-bot+netdevbpf
3 siblings, 1 reply; 7+ messages in thread
From: Alexei Starovoitov @ 2024-01-09 2:16 UTC (permalink / raw)
To: Dave Thaler; +Cc: bpf, bpf, Dave Thaler
On Mon, Jan 8, 2024 at 1:42 PM Dave Thaler
<dthaler1968=40googlemail.com@dmarc.ietf.org> wrote:
>
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Nice start. lgtm.
Waiting for acks...
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
2024-01-09 2:16 ` Alexei Starovoitov
@ 2024-01-09 2:16 ` Alexei Starovoitov
0 siblings, 0 replies; 7+ messages in thread
From: Alexei Starovoitov @ 2024-01-09 2:16 UTC (permalink / raw)
To: Dave Thaler; +Cc: bpf, bpf, Dave Thaler
On Mon, Jan 8, 2024 at 1:42 PM Dave Thaler
<dthaler1968=40googlemail.com@dmarc.ietf.org> wrote:
>
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Nice start. lgtm.
Waiting for acks...
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
2024-01-08 21:42 [PATCH bpf-next] Introduce concept of conformance groups Dave Thaler
2024-01-08 21:42 ` [Bpf] " Dave Thaler
2024-01-09 2:16 ` Alexei Starovoitov
@ 2024-01-09 16:10 ` David Vernet
2024-01-09 16:10 ` David Vernet
2024-01-12 2:40 ` patchwork-bot+netdevbpf
3 siblings, 1 reply; 7+ messages in thread
From: David Vernet @ 2024-01-09 16:10 UTC (permalink / raw)
To: Dave Thaler; +Cc: bpf, bpf, Dave Thaler
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Mon, Jan 08, 2024 at 01:42:31PM -0800, Dave Thaler wrote:
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Acked-by: David Vernet <void@manifault.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
2024-01-09 16:10 ` David Vernet
@ 2024-01-09 16:10 ` David Vernet
0 siblings, 0 replies; 7+ messages in thread
From: David Vernet @ 2024-01-09 16:10 UTC (permalink / raw)
To: Dave Thaler; +Cc: bpf, bpf, Dave Thaler
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
On Mon, Jan 08, 2024 at 01:42:31PM -0800, Dave Thaler wrote:
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Acked-by: David Vernet <void@manifault.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 76 bytes --]
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH bpf-next] Introduce concept of conformance groups
2024-01-08 21:42 [PATCH bpf-next] Introduce concept of conformance groups Dave Thaler
` (2 preceding siblings ...)
2024-01-09 16:10 ` David Vernet
@ 2024-01-12 2:40 ` patchwork-bot+netdevbpf
3 siblings, 0 replies; 7+ messages in thread
From: patchwork-bot+netdevbpf @ 2024-01-12 2:40 UTC (permalink / raw)
To: Dave Thaler; +Cc: bpf, bpf, dthaler1968
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 8 Jan 2024 13:42:31 -0800 you wrote:
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next] Introduce concept of conformance groups
https://git.kernel.org/bpf/bpf-next/c/fd707fb8dc24
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2024-01-12 2:40 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-08 21:42 [PATCH bpf-next] Introduce concept of conformance groups Dave Thaler
2024-01-08 21:42 ` [Bpf] " Dave Thaler
2024-01-09 2:16 ` Alexei Starovoitov
2024-01-09 2:16 ` Alexei Starovoitov
2024-01-09 16:10 ` David Vernet
2024-01-09 16:10 ` David Vernet
2024-01-12 2:40 ` patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).