From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: bpf <bpf@vger.kernel.org>, linux-kernel@vger.kernel.org
Cc: Kernel Team <kernel-team@meta.com>,
kernel-ci@meta.com, Alexei Starovoitov <ast@kernel.org>,
tj@kernel.org, mkutsevol@meta.com, scottbpc@meta.com,
jakehillion@meta.com, mykolal@meta.com
Subject: BPF CI update: veristat-scx job
Date: Mon, 9 Jun 2025 14:30:19 -0700 [thread overview]
Message-ID: <c17b2e6c-3626-4d69-8784-01b13a9e2851@linux.dev> (raw)
Hi everyone.
In effort to improve testing of both BPF subsystem and sched-ext
project [1], a new testing workflow has been added to BPF CI:
veristat-scx.
veristat-kernel and veristat-meta jobs have been running for a while
now, and veristat-scx is basically adding more test cases using
sched-ext BPF programs as input.
For those who aren't aware, veristat [2] is a command line tool that
can be used to load BPF object files into the kernel and check
verification results, among other things. It's source code is at
./tools/testing/selftests/bpf/veristat.c
On BPF CI, veristat-${target} job takes BPF object files (determined
by ${target}) as input, and runs veristat on them against the kernel
under testing. In addition to checking whether BPF program is accepted
by the verifier, the CI job also collects verifier performance stats,
and compares them to the baseline *failing* if a significant
regression is detected.
See an example of successful job run here:
https://github.com/kernel-patches/bpf/actions/runs/15543439297/job/43761685117
[1] https://github.com/sched-ext/scx
[2] https://github.com/libbpf/veristat
next reply other threads:[~2025-06-09 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 21:30 Ihor Solodrai [this message]
2025-06-09 21:43 ` BPF CI update: veristat-scx job Andrii Nakryiko
2025-06-09 21:49 ` Ihor Solodrai
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=c17b2e6c-3626-4d69-8784-01b13a9e2851@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jakehillion@meta.com \
--cc=kernel-ci@meta.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkutsevol@meta.com \
--cc=mykolal@meta.com \
--cc=scottbpc@meta.com \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.