[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211007080952.1255615-1-davemarchevsky@fb.com>
Date: Thu, 7 Oct 2021 01:09:50 -0700
From: Dave Marchevsky <davemarchevsky@...com>
To: <bpf@...r.kernel.org>
CC: <netdev@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
Dave Marchevsky <davemarchevsky@...com>
Subject: [PATCH bpf-next 0/2] bpf: keep track of verifier insn_processed
This is a followup to discussion around RFC patchset "bpf: keep track of
prog verification stats" [0]. The RFC elaborates on my usecase, but to
summarize: keeping track of verifier stats for programs as they - and
the kernels they run on - change over time can help developers of
individual programs and BPF kernel folks.
The RFC added a verif_stats to the uapi which contained most of the info
which verifier prints currently. Feedback here was to avoid polluting
uapi with stats that might be meaningless after major changes to the
verifier, but that insn_processed or conceptually similar number would
exist in the long term and was safe to expose.
So let's expose just insn_processed via bpf_prog_info and fdinfo for now
and explore good ways of getting more complicated stats in the future.
[0] https://lore.kernel.org/bpf/20210920151112.3770991-1-davemarchevsky@fb.com/
Dave Marchevsky (2):
bpf: add insn_processed to bpf_prog_info and fdinfo
selftests/bpf: add verif_stats test
include/linux/bpf.h | 1 +
include/uapi/linux/bpf.h | 1 +
kernel/bpf/syscall.c | 8 +++--
kernel/bpf/verifier.c | 1 +
tools/include/uapi/linux/bpf.h | 1 +
.../selftests/bpf/prog_tests/verif_stats.c | 31 +++++++++++++++++++
6 files changed, 41 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/verif_stats.c
--
2.30.2
Powered by blists - more mailing lists