From: Daniel Borkmann <dborkman@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Zi Shen Lim <zlim.lnx@gmail.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@plumgrid.com>,
Chema Gonzalez <chema@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH RFC] arm64: eBPF JIT compiler
Date: Thu, 03 Jul 2014 11:23:14 +0200 [thread overview]
Message-ID: <53B52102.7060400@redhat.com> (raw)
In-Reply-To: <20140703091450.GB12958@arm.com>
On 07/03/2014 11:14 AM, Will Deacon wrote:
> On Wed, Jul 02, 2014 at 06:20:24AM +0100, Zi Shen Lim wrote:
>> The JIT compiler emits A64 instructions. It supports eBPF only.
>> Legacy BPF is supported thanks to conversion by BPF core.
>>
>> JIT is enabled in the same way as for other architectures:
>>
>> echo 1 > /proc/sys/net/core/bpf_jit_enable
>>
>> Or for additional compiler output:
>>
>> echo 2 > /proc/sys/net/core/bpf_jit_enable
>>
>> See Documentation/networking/filter.txt for more information.
>>
>> The implementation passes all 57 tests in lib/test_bpf.c
>> on ARMv8 Foundation Model :)
>
> First off, this is really cool. Thanks for putting in the effort to get this
> supported on arm64! I'm happy to run tests on some real hardware if you tell
> me how to run them :)
We have lib/test_bpf.c for this, see also Documentation/networking/filter.txt.
So, the procedure would be, e.g.:
1) echo 1 > /proc/sys/net/core/bpf_jit_enable
2) modprobe/insmod test_bpf
3) See kernel log for passes/fails
For seccomp/BPF, there's a test suite in:
https://github.com/redpig/seccomp
next prev parent reply other threads:[~2014-07-03 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 5:20 [PATCH RFC] arm64: eBPF JIT compiler Zi Shen Lim
2014-07-02 5:38 ` Alexei Starovoitov
2014-07-02 21:28 ` Alexei Starovoitov
2014-07-03 4:57 ` Z Lim
2014-07-03 5:21 ` Z Lim
2014-07-03 9:14 ` Will Deacon
2014-07-03 9:23 ` Daniel Borkmann [this message]
2014-07-04 6:56 ` Z Lim
2014-07-04 8:07 ` Will Deacon
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=53B52102.7060400@redhat.com \
--to=dborkman@redhat.com \
--cc=Catalin.Marinas@arm.com \
--cc=ast@plumgrid.com \
--cc=chema@google.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=zlim.lnx@gmail.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 NNTP newsgroup(s).