summaryrefslogtreecommitdiff
path: root/scripts/mkversion
diff options
context:
space:
mode:
authorDaniel Borkmann <daniel@iogearbox.net>2015-04-30 16:17:27 +0200
committerDavid S. Miller <davem@davemloft.net>2015-04-30 16:40:53 -0400
commit327941f8d322685633f74fb43dc3aec86529f5f4 (patch)
tree7d1f9a31e058fc314a5e4426a322889a4636a961 /scripts/mkversion
parent18824894dbec3eb2202fc92d52a0c8bd27c8a63f (diff)
test_bpf: indicate whether bpf prog got jited in test suite
I think this is useful to verify whether a filter could be JITed or not in case of bpf_prog_enable >= 1, which otherwise the test suite doesn't tell besides taking a good peek at the performance numbers. Nicolas Schichan reported a bug in the ARM JIT compiler that rejected and waved the filter to the interpreter although it shouldn't have. Nevertheless, the test passes as expected, but such information is not visible. It's i.e. useful for the remaining classic JITs, but also for implementing remaining opcodes that are not yet present in eBPF JITs (e.g. ARM64 waves some of them to the interpreter). This minor patch allows to grep through dmesg to find those accordingly, but also provides a total summary, i.e.: [<X>/53 JIT'ed] # echo 1 > /proc/sys/net/core/bpf_jit_enable # insmod lib/test_bpf.ko # dmesg | grep "jited:0" dmesg example on the ARM issue with JIT rejection: [...] [ 67.925387] test_bpf: #2 ADD_SUB_MUL_K jited:1 24 PASS [ 67.930889] test_bpf: #3 DIV_MOD_KX jited:0 794 PASS [ 67.943940] test_bpf: #4 AND_OR_LSH_K jited:1 20 20 PASS [...] Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Cc: Nicolas Schichan <nschichan@freebox.fr> Cc: Alexei Starovoitov <ast@plumgrid.com> Acked-by: Alexei Starovoitov <ast@plumgrid.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/mkversion')
0 files changed, 0 insertions, 0 deletions