From: Nick Clifton <nickc@redhat.com>
To: David Faust <david.faust@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH] bpf: add xBPF ISA
Date: Wed, 26 Aug 2020 14:07:11 +0100 [thread overview]
Message-ID: <be5fb277-2ed8-16b8-3b38-a6d3339cb032@redhat.com> (raw)
In-Reply-To: <20200825181747.57537-1-david.faust@oracle.com>
Hi David,
> This patch adds support for xBPF, another ISA targetting the BPF
> virtual architecture. For now, the primary difference between eBPF
> and xBPF is that xBPF supports indirect calls through the
> 'call %reg' form of the call instruction.
Approved - please apply, but with one small addition:
You missed out the "hack" in opcodes/disassemble.c for when building
with all architectures enabled. Ie you need to patch:
# ifdef ARCH_m32c
enum epbf_isa_attr
{
- ISA_EBPFLE, ISA_EBPFBE, ISA_EBPFMAX
+ ISA_EBPFLE, ISA_EBPFBE, ISA_XBPFLE, ISA_XBPFBE, ISA_EBPFMAX
};
# else
# include "bpf-desc.h"
Cheers
Nick
next prev parent reply other threads:[~2020-08-26 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 18:17 David Faust
2020-08-26 13:07 ` Nick Clifton [this message]
2020-08-26 14:51 ` Jose E. Marchesi
2020-08-26 13:45 ` Jose E. Marchesi
2020-08-26 14:27 ` Alan Modra
2020-08-26 15:40 ` 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=be5fb277-2ed8-16b8-3b38-a6d3339cb032@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=david.faust@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).