From: Christoph Hellwig <hch@infradead.org>
To: Will Hawkins <hawkinsw@obs.cr>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>,
"bpf@ietf.org" <bpf@ietf.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [Bpf] ISA RFC compliance question
Date: Mon, 23 Oct 2023 21:00:41 -0700 [thread overview]
Message-ID: <ZTdBacjsOq9MmXEg@infradead.org> (raw)
Message-ID: <20231024040041.mEANvbgcrPRH8_dar6EK9aUqq7iw0tO80fW9YpSxTVo@z> (raw)
In-Reply-To: <CADx9qWgP=h4kQEJ2Cpy-A9hyiKLdkF3hVZVydLrz2Lk+UGBaAQ@mail.gmail.com>
On Mon, Oct 23, 2023 at 11:06:32AM -0400, Will Hawkins wrote:
> Can we look to either RISC-V or ARM for prior art in how they worked
> different versions and compliance levels? I am happy to amass some
> documentation about their processes/procedures if you think that it
> would help!
I don't know arm to well. x86 is mostly discoverable by bits set in the
cpuid leaves, and RISC-V has formal extensions, initially letter and
after they noticed that isn't fine grained enough a lot of Z-prefixed
ones. I think RISC-V is a good starting point:
https://en.wikichip.org/wiki/risc-v/standard_extensions
we need to be very careful on what are good scopes for extensions so
they are on the one hand useful, but on the other hand not too many
of them so that we stop being easily interoperable.
As seen in the other branch of this discussion we should also thing
a bit of what is supported by existing implementations. I don't think
it is a non-startert if they become non-compliant, but we need to weight
this very carefully.
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-10-24 4:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 20:14 [Bpf] ISA RFC compliance question Dave Thaler
2023-09-29 20:17 ` Dave Thaler
2023-09-29 20:17 ` [Bpf] " Dave Thaler
2023-09-30 15:48 ` Alexei Starovoitov
2023-09-30 15:48 ` Alexei Starovoitov
2023-10-05 20:14 ` Dave Thaler
2023-10-05 20:14 ` Dave Thaler
2023-10-06 23:06 ` Alexei Starovoitov
2023-10-06 23:06 ` Alexei Starovoitov
2023-10-23 22:15 ` David Vernet
2023-10-23 22:15 ` David Vernet
2023-10-19 6:02 ` Christoph Hellwig
2023-10-19 6:02 ` Christoph Hellwig
2023-10-23 15:06 ` Will Hawkins
2023-10-23 15:06 ` Will Hawkins
2023-10-24 4:00 ` Christoph Hellwig [this message]
2023-10-24 4:00 ` Christoph Hellwig
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=ZTdBacjsOq9MmXEg@infradead.org \
--to=hch@infradead.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler=40microsoft.com@dmarc.ietf.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).