From: David Miller <davem@davemloft.net>
To: ast@fb.com
Cc: daniel@iogearbox.net, aconole@bytheb.org, netdev@vger.kernel.org,
xdp-newbies@vger.kernel.org
Subject: Re: [PATCH v3 binutils] Add BPF support to binutils...
Date: Sun, 30 Apr 2017 11:40:24 -0400 (EDT) [thread overview]
Message-ID: <20170430.114024.1304052185817716163.davem@davemloft.net> (raw)
In-Reply-To: <76ed19a7-add3-0642-4298-9402c7ff0be8@fb.com>
From: Alexei Starovoitov <ast@fb.com>
Date: Sat, 29 Apr 2017 23:44:59 -0700
> On 4/29/17 7:37 PM, David Miller wrote:
>> BTW, should I just remove tailcall from the opcode table altogether?
>
> yeah. tailcall is not a special opcode from user space point of view.
> Only after normal call with func_id=bpf_tail_call passes verifier
> then verifier will change insn->code into CALL|X
> It's done only to have two 'case' statement in the interpreter,
> so that normal calls and tailcalls don't interfere.
> From user space pov CALL|X opcode is reserved and we can use it
> for something in the future. Just need to change interpeter and JITs.
Ok, I've removed it from my tree.
Thanks.
next prev parent reply other threads:[~2017-04-30 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 20:33 [PATCH v3 binutils] Add BPF support to binutils David Miller
2017-04-30 0:48 ` Alexei Starovoitov
2017-04-30 2:11 ` David Miller
2017-04-30 2:13 ` David Miller
2017-04-30 2:24 ` Alexei Starovoitov
2017-04-30 2:24 ` David Miller
2017-04-30 2:37 ` David Miller
2017-04-30 6:44 ` Alexei Starovoitov
2017-04-30 15:28 ` David Miller
2017-04-30 15:40 ` David Miller [this message]
2017-04-30 18:21 ` David Miller
2017-05-02 2:49 ` Alexei Starovoitov
2017-05-02 3:03 ` David Miller
2017-05-02 3:14 ` Alexei Starovoitov
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=20170430.114024.1304052185817716163.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aconole@bytheb.org \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=xdp-newbies@vger.kernel.org \
/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).