From: Denis Kirjanov <kda@linux-powerpc.org>
To: netdev@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH net-next 0/6] bpf: Enable BPF JIT on ppc32
Date: Sun, 15 Feb 2015 21:06:39 +0300 [thread overview]
Message-ID: <1424023605-2416-1-git-send-email-kda@linux-powerpc.org> (raw)
This patch series enables BPF JIT on ppc32. There are relatevily
few chnages in the code to make it work.
All test_bpf tests passed both on 7447a and P2041-based machines.
arch/powerpc/Kconfig | 2 +-
arch/powerpc/include/asm/asm-compat.h | 4 +
arch/powerpc/include/asm/ppc-opcode.h | 2 +
arch/powerpc/net/Makefile | 2 +-
arch/powerpc/net/bpf_jit.h | 47 ++++++-
arch/powerpc/net/bpf_jit_64.S | 229 ----------------------------------
arch/powerpc/net/bpf_jit_asm.S | 229 ++++++++++++++++++++++++++++++++++
arch/powerpc/net/bpf_jit_comp.c | 32 ++---
8 files changed, 300 insertions(+), 247 deletions(-)
next reply other threads:[~2015-02-15 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 18:06 Denis Kirjanov [this message]
2015-02-15 18:06 ` [PATCH net-next 1/6] ppc: Kconfig: Enable BPF JIT on ppc32 Denis Kirjanov
2015-02-15 18:15 ` Joe Perches
2015-02-15 19:07 ` David Miller
2015-02-15 19:16 ` Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 2/6] ppc: bpf: add required compatibility macros for jit Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 3/6] ppc: bpf: add reqired opcodes for ppc32 Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 4/6] ppc: bpf: update jit to use compatibility macros Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 5/6] ppc: bpf: rename bpf_jit_64.S to bpf_jit_asm.S Denis Kirjanov
2015-02-15 18:06 ` [PATCH net-next 6/6] ppc: bpf: Add SKF_AD_CPU for ppc32 Denis Kirjanov
2015-02-15 20:09 ` [PATCH net-next 0/6] bpf: Enable BPF JIT on ppc32 Daniel Borkmann
2015-02-16 7:13 ` Denis Kirjanov
2015-02-16 16:01 ` Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2015-02-16 15:02 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=1424023605-2416-1-git-send-email-kda@linux-powerpc.org \
--to=kda@linux-powerpc.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@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).