From: Daniel Wagner <dwagner@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
Stephen Zhang <starzhangzsd@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Coly Li <colyli@fnnas.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
linux-block@vger.kernel.org, linux-bcache@vger.kernel.org,
Daniel Wagner <dwagner@suse.de>
Subject: [PATCH blktests v3 3/3] doc: document how to configure bcache tests
Date: Thu, 22 Jan 2026 10:57:14 +0100 [thread overview]
Message-ID: <20260122-bcache-v3-3-2c02d15a4503@suse.de> (raw)
In-Reply-To: <20260122-bcache-v3-0-2c02d15a4503@suse.de>
Add a bcache entry in running-tests which explains how to configure
blktests for the bcache tests.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
Documentation/running-tests.md | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/Documentation/running-tests.md b/Documentation/running-tests.md
index f9da042bb3a0..c4abc6767cd0 100644
--- a/Documentation/running-tests.md
+++ b/Documentation/running-tests.md
@@ -189,6 +189,22 @@ THROTL_BLKDEV_TYPES="sdebug" ./check throtl/
THROTL_BLKDEV_TYPES="nullb sdebug" ./check throtl/
```
+### bcache test configuration
+
+The bcache tests require multiple devices to run simultaneously. By default,
+blktests executes each test case iteratively for every individual device listed
+in TEST_DEVS. This standard behavior makes it impossible to pass a group of
+devices into a single test via TEST_DEVS.
+
+To solve this, the TEST_CASE_DEV_ARRAY was introduced. This allows for custom
+device configurations on a per-test basis. For bcache tests, a minimum of three
+devices is required. Configuration Example
+
+Add the following to your configuration to define the devices used for all
+bcache tests:
+
+TEST_CASE_DEV_ARRAY[bcache/*]="/dev/nvme0n1 /dev/vdb /dev/vdc"
+
### Normal user
To run test cases which require normal user privilege, prepare a user and
--
2.52.0
prev parent reply other threads:[~2026-01-22 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:57 [PATCH blktests v3 0/3] bcache: add initial test cases Daniel Wagner
2026-01-22 9:57 ` [PATCH blktests v3 1/3] bcache: add bcache/001 Daniel Wagner
2026-01-22 9:57 ` [PATCH blktests v3 2/3] bcache: add bcache/002 Daniel Wagner
2026-01-22 9:57 ` Daniel Wagner [this message]
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=20260122-bcache-v3-3-2c02d15a4503@suse.de \
--to=dwagner@suse.de \
--cc=Johannes.Thumshirn@wdc.com \
--cc=colyli@fnnas.com \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=starzhangzsd@gmail.com \
/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