From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: alison@she-devel.com, juri.lelli@arm.com, fengc@google.com,
daniel@iogearbox.net, davem@davemloft.net, ast@kernel.org,
kernel-team@android.com, Joel Fernandes <joelaf@google.com>
Subject: [PATCH v4 0/4] Add cross-compilation support to eBPF samples
Date: Wed, 20 Sep 2017 09:04:32 -0700 [thread overview]
Message-ID: <20170920160436.24689-1-joelaf@google.com> (raw)
These patches fix issues seen when cross-compiling eBPF samples on arm64.
Compared to [1], I dropped the controversial inline-asm patch and exploring
other options to fix it. However these patches are a step in the right
direction and I look forward to getting them into -next and the merge window.
Changes since v3:
- just a repost with acks
[1] https://lkml.org/lkml/2017/8/7/417
Joel Fernandes (4):
samples/bpf: Use getppid instead of getpgrp for array map stress
samples/bpf: Enable cross compiler support
samples/bpf: Fix pt_regs issues when cross-compiling
samples/bpf: Add documentation on cross compilation
samples/bpf/Makefile | 7 +++-
samples/bpf/README.rst | 10 ++++++
samples/bpf/map_perf_test_kern.c | 2 +-
samples/bpf/map_perf_test_user.c | 2 +-
tools/testing/selftests/bpf/bpf_helpers.h | 56 +++++++++++++++++++++++++++----
5 files changed, 67 insertions(+), 10 deletions(-)
--
2.14.1.821.g8fa685d3b7-goog
next reply other threads:[~2017-09-20 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 16:04 Joel Fernandes [this message]
2017-09-21 18:59 ` [PATCH v4 0/4] Add cross-compilation support to eBPF samples David Miller
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=20170920160436.24689-1-joelaf@google.com \
--to=joelaf@google.com \
--cc=alison@she-devel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=fengc@google.com \
--cc=juri.lelli@arm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.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).