From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Subject: [PATCH v2 net-next 0/2] sparc64 eBPF JIT
Date: Fri, 21 Apr 2017 20:16:48 -0700 (PDT) [thread overview]
Message-ID: <20170421.201648.1153236027978111172.davem@davemloft.net> (raw)
This series adds an eBPF JIT for sparc64.
Sparc32 keeps having it's cBPF JIT after these changes.
Thanks to Daniel and Alexei for their invaluable feedback and review.
Signed-off-by: David S. Miller <davem@davemloft.net>
---
since v1:
-- add tail call support
-- fix MOD generation to not emit the same constant load several times
-- flush icache over entire buffer properly
-- do STACK_BIAS adjustment of FP once in prologue
-- remove useless sanity checks
-- generate patches with -M -C
since RFC:
-- rework register allocation so that we don't have to emit move
instructions to get the arguments into place for calls
-- allow FP as source for 64-bit ALU move operations
-- don't emit NOP instructions in prologue, instead do multiple
passes so that all the branch offsets settle down
-- remove unnecessary checks on imm64 loads that verifier does
-- consistently use bpf2sparc[] instead of direct register references
reply other threads:[~2017-04-22 3:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170421.201648.1153236027978111172.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@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