From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFCv2] arm64: eBPF JIT compiler
Date: Wed, 9 Jul 2014 14:00:17 +0100 [thread overview]
Message-ID: <20140709130017.GL9485@arm.com> (raw)
In-Reply-To: <1404803213-10653-1-git-send-email-zlim.lnx@gmail.com>
On Tue, Jul 08, 2014 at 08:06:53AM +0100, Zi Shen Lim wrote:
> * Per discussion with Will, I'll also look into consolidating
> bpf_jit.h into arch/arm64/kernel/insn.{c,h}.
I'm happy to review this once you have something ready.
> FUTURE WORK:
>
> 1. Implement remaining classes of eBPF instructions: ST|MEM, STX|XADD
> which currently do not have corresponding test cases in test_bpf.
I can help out with atomics, if you need it. Are the memory barrier
semantics well-defined for eBPF?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Zi Shen Lim <zlim.lnx@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <dborkman@redhat.com>,
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 RFCv2] arm64: eBPF JIT compiler
Date: Wed, 9 Jul 2014 14:00:17 +0100 [thread overview]
Message-ID: <20140709130017.GL9485@arm.com> (raw)
In-Reply-To: <1404803213-10653-1-git-send-email-zlim.lnx@gmail.com>
On Tue, Jul 08, 2014 at 08:06:53AM +0100, Zi Shen Lim wrote:
> * Per discussion with Will, I'll also look into consolidating
> bpf_jit.h into arch/arm64/kernel/insn.{c,h}.
I'm happy to review this once you have something ready.
> FUTURE WORK:
>
> 1. Implement remaining classes of eBPF instructions: ST|MEM, STX|XADD
> which currently do not have corresponding test cases in test_bpf.
I can help out with atomics, if you need it. Are the memory barrier
semantics well-defined for eBPF?
Will
next prev parent reply other threads:[~2014-07-09 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 7:06 [PATCH RFCv2] arm64: eBPF JIT compiler Zi Shen Lim
2014-07-08 7:06 ` Zi Shen Lim
2014-07-08 9:24 ` Alexei Starovoitov
2014-07-08 9:24 ` Alexei Starovoitov
2014-07-09 5:11 ` Z Lim
2014-07-09 5:11 ` Z Lim
2014-07-09 13:00 ` Will Deacon [this message]
2014-07-09 13:00 ` Will Deacon
2014-07-10 9:51 ` Alexei Starovoitov
2014-07-10 9:51 ` 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=20140709130017.GL9485@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.