[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c622d372-f4a8-e080-3843-df22f926142f@iogearbox.net>
Date: Wed, 11 Mar 2020 15:19:20 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Andrii Nakryiko <andriin@...com>, bpf@...r.kernel.org,
netdev@...r.kernel.org, ast@...com
Cc: andrii.nakryiko@...il.com, kernel-team@...com
Subject: Re: [PATCH bpf-next] tools/runqslower: add BPF_F_CURRENT_CPU for
running selftest on older kernels
On 3/11/20 5:30 AM, Andrii Nakryiko wrote:
> Libbpf compiles and runs subset of selftests on each PR in its Github mirror
> repository. To allow still building up-to-date selftests against outdated
> kernel images, add back BPF_F_CURRENT_CPU definitions back.
>
> N.B. BCC's runqslower version ([0]) doesn't need BPF_F_CURRENT_CPU due to use of
> locally checked in vmlinux.h, generated against kernel with 1aae4bdd7879 ("bpf:
> Switch BPF UAPI #define constants used from BPF program side to enums")
> applied.
>
> [0] https://github.com/iovisor/bcc/pull/2809
>
> Fixes: 367d82f17eff (" tools/runqslower: Drop copy/pasted BPF_F_CURRENT_CPU definiton")
> Signed-off-by: Andrii Nakryiko <andriin@...com>
Too bad, applied, thanks!
Powered by blists - more mailing lists