From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@lst.de>,
Eric Biggers <ebiggers@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: [PATCH] raid/kunit: Enable RAID6 PQ and XOR benchmarks if KUNIT_ALL_TESTS=m
Date: Wed, 26 Aug 2026 20:50:58 -0700 [thread overview]
Message-ID: <20260826205058.a6ff019d0584f75c7f50430b@linux-foundation.org> (raw)
In-Reply-To: <64c6e0191bd8ccef0074ffbb09bd0584680d710b.1787584360.git.geert@linux-m68k.org>
On Mon, 24 Aug 2026 17:14:01 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Enabling the (possibly long-running benchmarks) by default may cause a
> big delay in boot time in case of built-in tests. However, they can
> still safely be enabled by default if all tests are modular, as they
> would only run when requested explicitly by the system administrator.
>
> ...
>
> --- a/lib/raid/Kconfig
> +++ b/lib/raid/Kconfig
> @@ -32,6 +32,7 @@ config XOR_KUNIT_TEST
> config XOR_BENCHMARK
> bool "Benchmark for xor_gen"
> depends on XOR_KUNIT_TEST
> + default y if KUNIT_ALL_TESTS=m
> help
> Include benchmarks in the KUnit test suite for xor_gen.
>
> @@ -63,6 +64,7 @@ config RAID6_PQ_KUNIT_TEST
> config RAID6_PQ_KUNIT_BENCHMARK
> bool "Benchmark for RAID6 PQ"
> depends on RAID6_PQ_KUNIT_TEST
> + default y if KUNIT_ALL_TESTS=m
> help
> Include benchmarks in the KUnit test suite for raid P/Q generation.
OK, thanks, but...
hp2:/usr/src/mm> scripts/get_maintainer.pl -f --no-rolestats lib/raid
[not linux-raid@vger.kernel.org]
Patches enthusiastically accepted ;)
next prev parent reply other threads:[~2026-08-27 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 15:14 Geert Uytterhoeven
2026-08-25 8:01 ` Christoph Hellwig
2026-08-25 8:32 ` Ard Biesheuvel
2026-08-27 3:50 ` Andrew Morton [this message]
2026-08-27 7:21 ` Geert Uytterhoeven
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=20260826205058.a6ff019d0584f75c7f50430b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-raid@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®