From: Paul Burton <paul.burton@mips.com>
To: Jiong Wang <jiong.wang@netronome.com>
Cc: "daniel@iogearbox.net" <daniel@iogearbox.net>,
"ast@kernel.org" <ast@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"oss-drivers@netronome.com" <oss-drivers@netronome.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH bpf-next 1/7] mips: bpf: implement jitting of BPF_ALU | BPF_ARSH | BPF_X
Date: Wed, 5 Dec 2018 00:02:51 +0000 [thread overview]
Message-ID: <20181205000250.mc6aw6odykynadkg@pburton-laptop> (raw)
In-Reply-To: <1543956922-8620-2-git-send-email-jiong.wang@netronome.com>
Hi Jiong,
On Tue, Dec 04, 2018 at 03:55:16PM -0500, Jiong Wang wrote:
> Jitting of BPF_K is supported already, but not BPF_X. This patch complete
> the support for the latter on both MIPS and microMIPS.
>
> Cc: Paul Burton <paul.burton@mips.com>
> Cc: linux-mips@vger.kernel.org
> Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
> ---
> arch/mips/include/asm/uasm.h | 1 +
> arch/mips/include/uapi/asm/inst.h | 1 +
> arch/mips/mm/uasm-micromips.c | 1 +
> arch/mips/mm/uasm-mips.c | 1 +
> arch/mips/mm/uasm.c | 9 +++++----
> arch/mips/net/ebpf_jit.c | 4 ++++
> 6 files changed, 13 insertions(+), 4 deletions(-)
I don't seem to have been copied on the rest of the series, but this
patch standalone looks good from a MIPS standpoint. If the series is
going through the net tree (and again, I can't see whether that seems
likely because I don't have the rest of the series) then:
Acked-by: Paul Burton <paul.burton@mips.com>
If you want me to take this patch through the MIPS tree instead then let
me know.
Thanks,
Paul
next prev parent reply other threads:[~2018-12-05 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1543956922-8620-1-git-send-email-jiong.wang@netronome.com>
2018-12-04 20:55 ` [PATCH bpf-next 1/7] mips: bpf: implement jitting of BPF_ALU | BPF_ARSH | BPF_X Jiong Wang
2018-12-05 0:02 ` Paul Burton [this message]
2018-12-05 11:07 ` Jiong Wang
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=20181205000250.mc6aw6odykynadkg@pburton-laptop \
--to=paul.burton@mips.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jiong.wang@netronome.com \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).