Re: [PATCH v4 17/21] perf tests: Introduce a 'needs_mlock' suite flag

[sashiko-bot@kernel.org]

> From: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> Each perf instance maps one ring buffer per CPU, all charged to the same
> per user budget set in kernel.perf_event_mlock_kb, so suites that map
> them need to be told apart from the ones that don't, to later have them
> take turns using that budget while the other tests keep running in
> parallel.
> 
> Add the flag to 'struct test_suite' and a DEFINE_SUITE_NEEDS_MLOCK()
> variant for the suites using the DEFINE_SUITE() form.
> 
> Shell tests run perf, that maps ring buffers, so they are taken to need
> room in that budget by default; the requisites, a comma separated list in
> the parens ending their description line, name what a test needs and take
> a "no_" prefix to waive it, e.g.:
> 
>   # perf stat tests (no_mlock)
> 
> "mlock" is room in that budget, so stating it only spells the default
> out, "no_mlock" waives it, and "exclusive" is the catch-all that keeps a
> test from running alongside any other, so it runs alone, in sequence, and
> implies every other requisite, which is why it can't be waived either.
> More requisites are to come, each stating what a test needs, till the
> catch-all isn't needed anymore.
> 
> 'perf test requisites' lists what each test needs, reusing the listing
> routine and taking the same test name fragments and numbers as 'list'.
> 
> Assisted-by: LLM
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261016212102.76550-1-acme@kernel.org?part=17