bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Will Hawkins <hawkinsw@obs.cr>
Cc: bpf@ietf.org, bpf <bpf@vger.kernel.org>
Subject: Re: [Bpf] [PATCH v3] bpf, docs: Add additional ABI working draft base text
Date: Sun, 5 Nov 2023 01:51:19 -0800	[thread overview]
Message-ID: <CAADnVQLztq5W9qmGUBQeRBUJeCmTcc9H-OXCCJJzn=0baz+8_Q@mail.gmail.com> (raw)
In-Reply-To: <20231103212024.327833-1-hawkinsw@obs.cr>

On Fri, Nov 3, 2023 at 2:20 PM Will Hawkins <hawkinsw@obs.cr> wrote:
> +
> +The ABI is specified in two parts: a generic part and a processor-specific part.
> +A pairing of generic ABI with the processor-specific ABI for a certain
> +instantiation of a BPF machine represents a complete binary interface for BPF
> +programs executing on that machine.
> +
> +This document is the generic ABI and specifies the parameters and behavior
> +common to all instantiations of BPF machines. In addition, it defines the
> +details that must be specified by each processor-specific ABI.
> +
> +These psABIs are the second part of the ABI. Each instantiation of a BPF
> +machine must describe the mechanism through which binary interface
> +compatibility is maintained with respect to the issues highlighted by this
> +document. However, the details that must be defined by a psABI are a minimum --
> +a psABI may specify additional requirements for binary interface compatibility
> +on a platform.

I don't understand what you are trying to say in the above.
In my mind there is only one BPF psABI and it doesn't have
generic and processor parts. There is only one "processor".
BPF is such a processor.

WARNING: multiple messages have this Message-ID (diff)
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Will Hawkins <hawkinsw@obs.cr>
Cc: bpf@ietf.org, bpf <bpf@vger.kernel.org>
Subject: Re: [Bpf] [PATCH v3] bpf, docs: Add additional ABI working draft base text
Date: Sun, 5 Nov 2023 01:51:19 -0800	[thread overview]
Message-ID: <CAADnVQLztq5W9qmGUBQeRBUJeCmTcc9H-OXCCJJzn=0baz+8_Q@mail.gmail.com> (raw)
Message-ID: <20231105095119.fclnjminEzXWETidit3A9sucp8Qzdk7iR8guwtqpqUE@z> (raw)
In-Reply-To: <20231103212024.327833-1-hawkinsw@obs.cr>

On Fri, Nov 3, 2023 at 2:20 PM Will Hawkins <hawkinsw@obs.cr> wrote:
> +
> +The ABI is specified in two parts: a generic part and a processor-specific part.
> +A pairing of generic ABI with the processor-specific ABI for a certain
> +instantiation of a BPF machine represents a complete binary interface for BPF
> +programs executing on that machine.
> +
> +This document is the generic ABI and specifies the parameters and behavior
> +common to all instantiations of BPF machines. In addition, it defines the
> +details that must be specified by each processor-specific ABI.
> +
> +These psABIs are the second part of the ABI. Each instantiation of a BPF
> +machine must describe the mechanism through which binary interface
> +compatibility is maintained with respect to the issues highlighted by this
> +document. However, the details that must be defined by a psABI are a minimum --
> +a psABI may specify additional requirements for binary interface compatibility
> +on a platform.

I don't understand what you are trying to say in the above.
In my mind there is only one BPF psABI and it doesn't have
generic and processor parts. There is only one "processor".
BPF is such a processor.

-- 
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf

  parent reply	other threads:[~2023-11-05  9:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 14:19 [PATCH] bpf, docs: Add additional ABI working draft base text Will Hawkins
2023-10-02 14:19 ` [Bpf] " Will Hawkins
2023-10-03 18:26 ` David Vernet
2023-10-03 18:26   ` [Bpf] " David Vernet
2023-10-21 23:13   ` Will Hawkins
2023-10-21 23:13     ` [Bpf] " Will Hawkins
2023-10-21 23:26     ` [PATCH v2] " Will Hawkins
2023-10-21 23:26       ` [Bpf] " Will Hawkins
2023-10-24  0:55     ` [PATCH] " David Vernet
2023-10-24  0:55       ` [Bpf] " David Vernet
2023-10-24  4:02       ` Christoph Hellwig
2023-10-24  4:02         ` Christoph Hellwig
2023-11-03 21:14       ` Will Hawkins
2023-11-03 21:14         ` Will Hawkins
2023-11-03 21:20         ` [PATCH v3] " Will Hawkins
2023-11-03 21:20           ` [Bpf] " Will Hawkins
2023-11-05  9:51           ` Alexei Starovoitov [this message]
2023-11-05  9:51             ` Alexei Starovoitov
2023-11-06  0:17             ` Will Hawkins
2023-11-06  0:17               ` Will Hawkins
2023-11-06  8:38               ` Alexei Starovoitov
2023-11-06  8:38                 ` Alexei Starovoitov
2023-11-07 19:56                 ` Will Hawkins
2023-11-07 19:56                   ` Will Hawkins
2023-11-08  1:17                   ` Alexei Starovoitov
2023-11-08  1:17                     ` Alexei Starovoitov
2023-11-08 10:13                     ` Will Hawkins
2023-11-08 10:13                       ` Will Hawkins
2023-11-08 19:51                       ` Alexei Starovoitov
2023-11-08 19:51                         ` Alexei Starovoitov
2023-11-08 23:57                         ` Will Hawkins
2023-11-08 23:57                           ` Will Hawkins
2023-11-09 18:31                           ` Alexei Starovoitov
2023-11-09 18:31                             ` Alexei Starovoitov
2023-11-10  0:56                             ` Will Hawkins
2023-11-10  0:56                               ` Will Hawkins
2023-11-10  1:35                               ` Will Hawkins
2023-11-10  1:35                                 ` Will Hawkins
2023-10-19  6:01 ` [Bpf] [PATCH] " Christoph Hellwig
2023-10-19  6:01   ` Christoph Hellwig
2023-10-20  2:42   ` Will Hawkins
2023-10-20  2:42     ` Will Hawkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAADnVQLztq5W9qmGUBQeRBUJeCmTcc9H-OXCCJJzn=0baz+8_Q@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=bpf@ietf.org \
    --cc=bpf@vger.kernel.org \
    --cc=hawkinsw@obs.cr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).