From: David Miller <davem@davemloft.net>
To: alexei.starovoitov@gmail.com
Cc: jose.marchesi@oracle.com, bpf@vger.kernel.org
Subject: Re: EF_BPF_GNU_XBPF
Date: Wed, 02 Sep 2020 16:18:49 -0700 (PDT) [thread overview]
Message-ID: <20200902.161849.1363975274756227714.davem@davemloft.net> (raw)
In-Reply-To: <20200902203206.nx6ws4ixuo2bcic6@ast-mbp.dhcp.thefacebook.com>
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Date: Wed, 2 Sep 2020 13:32:06 -0700
> On Wed, Sep 02, 2020 at 10:19:58PM +0200, Jose E. Marchesi wrote:
>>
>> As such, the property of being verifiable is irrelevant.
>
> No. It's a fundamental property of BPF.
> If it's not verifiable it's not BPF. It's not xBPF either.
> Please call it something else and don't confuse people that your ISA
> has any overlap with BPF. It doesn't. It's not verifiable.
I have to agree with Alexei here. You are trying to create something
which is not fundamentally BPF and it will create a lot of confusion
and hardship on people who are working on BPF when you publish
binaries with this machine type.
Please don't do stuff like this, thank you.
next prev parent reply other threads:[~2020-09-02 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 18:18 EF_BPF_GNU_XBPF Jose E. Marchesi
2020-09-02 19:31 ` EF_BPF_GNU_XBPF Alexei Starovoitov
2020-09-02 20:19 ` EF_BPF_GNU_XBPF Jose E. Marchesi
2020-09-02 20:32 ` EF_BPF_GNU_XBPF Alexei Starovoitov
2020-09-02 21:17 ` EF_BPF_GNU_XBPF Jose E. Marchesi
2020-09-02 21:33 ` EF_BPF_GNU_XBPF Daniel Borkmann
2020-09-02 22:10 ` EF_BPF_GNU_XBPF Jose E. Marchesi
2020-09-02 23:22 ` EF_BPF_GNU_XBPF David Miller
2020-09-02 23:40 ` EF_BPF_GNU_XBPF Jose E. Marchesi
2020-09-02 23:20 ` EF_BPF_GNU_XBPF David Miller
2020-09-02 23:18 ` David Miller [this message]
2020-09-02 23:27 ` EF_BPF_GNU_XBPF Jose E. Marchesi
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=20200902.161849.1363975274756227714.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=jose.marchesi@oracle.com \
/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