* [PATCH RFC v3 0/4] Add cross-compilation support to eBPF samples
@ 2017-09-03 18:23 Joel Fernandes
2017-09-06 3:24 ` Alexei Starovoitov
0 siblings, 1 reply; 3+ messages in thread
From: Joel Fernandes @ 2017-09-03 18:23 UTC (permalink / raw)
To: linux-kernel, netdev
Cc: kernel-team, Juri Lelli, Alison Chaiken, Chenbo Feng,
Joel Fernandes, Alexei Starovoitov, Daniel Borkmann, David Miller
These patches fix issues seen when cross-compiling eBPF samples on arm64.
Compared to [1], I dropped the controversial inline-asm patch pending further
discussion on the right way to do it. However these patches are still a step in
the right direction and I wanted them to get in before the more controversial
bit.
[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(-)
CC: Alexei Starovoitov <ast@kernel.org>
CC: Daniel Borkmann <daniel@iogearbox.net>
Cc: David Miller <davem@davemloft.net>
--
2.14.1.581.gf28d330327-goog
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH RFC v3 0/4] Add cross-compilation support to eBPF samples
2017-09-03 18:23 [PATCH RFC v3 0/4] Add cross-compilation support to eBPF samples Joel Fernandes
@ 2017-09-06 3:24 ` Alexei Starovoitov
2017-09-06 3:27 ` Joel Fernandes
0 siblings, 1 reply; 3+ messages in thread
From: Alexei Starovoitov @ 2017-09-06 3:24 UTC (permalink / raw)
To: Joel Fernandes
Cc: linux-kernel, netdev, kernel-team, Juri Lelli, Alison Chaiken,
Chenbo Feng, Alexei Starovoitov, Daniel Borkmann, David Miller
On Sun, Sep 03, 2017 at 11:23:21AM -0700, Joel Fernandes wrote:
> These patches fix issues seen when cross-compiling eBPF samples on arm64.
> Compared to [1], I dropped the controversial inline-asm patch pending further
> discussion on the right way to do it. However these patches are still a step in
> the right direction and I wanted them to get in before the more controversial
> bit.
All patches in this set look good to me.
When you repost without changes after net-next reopens pls keep my:
Acked-by: Alexei Starovoitov <ast@kernel.org>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH RFC v3 0/4] Add cross-compilation support to eBPF samples
2017-09-06 3:24 ` Alexei Starovoitov
@ 2017-09-06 3:27 ` Joel Fernandes
0 siblings, 0 replies; 3+ messages in thread
From: Joel Fernandes @ 2017-09-06 3:27 UTC (permalink / raw)
To: Alexei Starovoitov
Cc: LKML, open list:BPF (Safe dynamic programs and tools),
kernel-team, Juri Lelli, Alison Chaiken, Chenbo Feng,
Alexei Starovoitov, Daniel Borkmann, David Miller
Hi Alexei,
On Tue, Sep 5, 2017 at 8:24 PM, Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
> On Sun, Sep 03, 2017 at 11:23:21AM -0700, Joel Fernandes wrote:
>> These patches fix issues seen when cross-compiling eBPF samples on arm64.
>> Compared to [1], I dropped the controversial inline-asm patch pending further
>> discussion on the right way to do it. However these patches are still a step in
>> the right direction and I wanted them to get in before the more controversial
>> bit.
>
> All patches in this set look good to me.
> When you repost without changes after net-next reopens pls keep my:
> Acked-by: Alexei Starovoitov <ast@kernel.org>
Thanks a lot! will do.
Regards,
Joel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-09-06 3:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-03 18:23 [PATCH RFC v3 0/4] Add cross-compilation support to eBPF samples Joel Fernandes
2017-09-06 3:24 ` Alexei Starovoitov
2017-09-06 3:27 ` Joel Fernandes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox