From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org
Cc: Chenbo Feng <fengc@google.com>,
Alison Chaiken <alison@she-devel.com>,
Juri Lelli <jlelli@google.com>,
Joel Fernandes <joelaf@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH RFC 0/5] add arm64 cross compilation support to BPF samples
Date: Mon, 7 Aug 2017 06:03:01 -0700 [thread overview]
Message-ID: <20170807130306.31530-1-joelaf@google.com> (raw)
The series adds cross compiler support for BPF samples and fixes issues
building for arm64.
Tested on my arm64 platform with good results, for x86 I have only build tested
it. There are no errors on building, however there is a build warning for x86
which I haven't yet gotten rid off (I believe the warning itself isn't of
consequence but rather a result of using the preprocessor in this way). I
appreciate any help testing for x86 and looking forward to any feedback on the
patches, thanks!
Joel Fernandes (5):
samples/bpf: Use getppid instead of getpgrp for array map stress
samples/bpf: Enable cross compiler support
samples/bpf: Fix inline asm issues building samples on arm64
samples/bpf: Fix pt_regs issues when cross-compiling
samples/bpf: Add documentation on cross compilation
samples/bpf/Makefile | 46 +++++++++++++++++++++++++-----
samples/bpf/README.rst | 10 +++++++
samples/bpf/arm64_asmstubs.h | 3 ++
samples/bpf/bpf_helpers.h | 61 ++++++++++++++++++++++++++++++++--------
samples/bpf/generic_asmstubs.h | 4 +++
samples/bpf/map_perf_test_kern.c | 2 +-
samples/bpf/map_perf_test_user.c | 2 +-
7 files changed, 107 insertions(+), 21 deletions(-)
create mode 100644 samples/bpf/arm64_asmstubs.h
create mode 100644 samples/bpf/generic_asmstubs.h
CC: Alexei Starovoitov <ast@kernel.org>
CC: Daniel Borkmann <daniel@iogearbox.net>
--
2.14.0.rc1.383.gd1ce394fe2-goog
next reply other threads:[~2017-08-07 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 13:03 Joel Fernandes [this message]
2017-08-07 13:03 ` [PATCH RFC 1/5] samples/bpf: Use getppid instead of getpgrp for array map stress Joel Fernandes
2017-08-07 13:03 ` [PATCH RFC 2/5] samples/bpf: Enable cross compiler support Joel Fernandes
2017-08-07 13:03 ` [PATCH RFC 3/5] samples/bpf: Fix inline asm issues building samples on arm64 Joel Fernandes
2017-08-07 13:03 ` [PATCH RFC 4/5] samples/bpf: Fix pt_regs issues when cross-compiling Joel Fernandes
2017-08-07 13:03 ` [PATCH RFC 5/5] samples/bpf: Add documentation on cross compilation Joel Fernandes
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=20170807130306.31530-1-joelaf@google.com \
--to=joelaf@google.com \
--cc=alison@she-devel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=fengc@google.com \
--cc=jlelli@google.com \
--cc=linux-kernel@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).