From: david.daney@cavium.com (David Daney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/3] bpf/arm64/mips: Avoid inline asm in BPF
Date: Thu, 15 Jun 2017 15:35:40 -0700 [thread overview]
Message-ID: <20170615223543.22867-1-david.daney@cavium.com> (raw)
To build samples/bpf on MIPS we need to avoid some inline asm that
causes llvm to fail.
Looking at the code, it seems that arm64 had the same problem and
avoided it by defining the header guard symbol. This approach does
not scale, so I invented a preprocessor define to identify the case of
building with a BPF target that can be used instead.
It is an RFC at this point as I haven't yet tested the arm64 change,
and I wanted to see if others think this is the proper way to handle
avoidance of inline asm.
David Daney (3):
arm64: Gate inclusion of asm/sysreg.h by __EMITTING_BPF__
samples/bpf: Add define __EMITTING_BPF__ when building BPF
MIPS: Include file changes to enable building BPF code with llvm
arch/arm64/include/asm/sysreg.h | 4 +++-
arch/mips/Makefile | 1 +
arch/mips/cavium-octeon/Platform | 3 +++
arch/mips/include/asm/checksum.h | 2 +-
arch/mips/include/uapi/asm/swab.h | 2 +-
samples/bpf/Makefile | 8 ++++----
6 files changed, 13 insertions(+), 7 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-15 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 22:35 David Daney [this message]
2017-06-15 22:35 ` [PATCH RFC 1/3] arm64: Gate inclusion of asm/sysreg.h by __EMITTING_BPF__ David Daney
2017-06-15 22:35 ` [PATCH RFC 2/3] samples/bpf: Add define __EMITTING_BPF__ when building BPF David Daney
2017-06-16 10:24 ` Daniel Borkmann
2017-06-16 16:14 ` David Miller
2017-06-19 14:37 ` Andy Gospodarek
2017-06-15 22:35 ` [PATCH RFC 3/3] MIPS: Include file changes to enable building BPF code with llvm David Daney
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=20170615223543.22867-1-david.daney@cavium.com \
--to=david.daney@cavium.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 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).