From: Bart Van Assche <bvanassche@acm.org>
To: Haris Iqbal <haris.iqbal@ionos.com>
Cc: "Shinichiro Kawasaki" <shinichiro.kawasaki@wdc.com>,
"Daniel Wagner" <dwagner@suse.de>,
"Chaitanya Kulkarni" <chaitanyak@nvidia.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"Hannes Reinecke" <hare@suse.de>, hch <hch@lst.de>,
"Jens Axboe" <axboe@kernel.dk>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"tytso@mit.edu" <tytso@mit.edu>,
"Johannes Thumshirn" <Johannes.Thumshirn@wdc.com>,
"Christian Brauner" <brauner@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Javier González" <javier@javigon.com>,
"willy@infradead.org" <willy@infradead.org>,
"Jan Kara" <jack@suse.cz>,
"amir73il@gmail.com" <amir73il@gmail.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"Damien Le Moal" <dlemoal@kernel.org>
Subject: Re: [LSF/MM/BPF ATTEND][LSF/MM/BPF TOPIC] : blktests: status, expansion plan for the storage stack test framework
Date: Wed, 25 Feb 2026 08:29:56 -0800 [thread overview]
Message-ID: <4bc30e61-e83d-4368-98bd-78f7d22c3f2e@acm.org> (raw)
In-Reply-To: <CAJpMwygzTcBnKVp=bJWZpW9X5JdcP9Lj4H1BRBu2bNV_kGyDQQ@mail.gmail.com>
On 2/25/26 2:07 AM, Haris Iqbal wrote:
> Regarding data modification, if the tests do not involve any crash or
> reboot, then the VMs can be started in "snapshot" mode.
I'm not sure that proposal makes sense. If e.g. an NVMe device is
specified in the blktests config file, it probably is the intention of
the person who runs the test to test the NVMe driver and/or the NVMe
device. Using any method to create a "snapshot" of the device and to
run blktests against that snapshot changes the kernel driver and also
the physical device that are tested. Not modifying the kernel driver
or physical device that are tested implies using PCIe passthrough. And
the PCIe passthrough mechanism can only be used by one VM at a time as
far as I know.
Bart.
next prev parent reply other threads:[~2026-02-25 16:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 20:35 [LSF/MM/BPF ATTEND][LSF/MM/BPF TOPIC] : blktests: status, expansion plan for the storage stack test framework Chaitanya Kulkarni
2026-02-12 7:52 ` Daniel Wagner
2026-02-12 7:57 ` Johannes Thumshirn
2026-02-13 17:30 ` Bart Van Assche
2026-02-13 17:35 ` James Bottomley
2026-02-13 11:23 ` Shinichiro Kawasaki
2026-02-13 14:18 ` Haris Iqbal
2026-02-15 18:38 ` Nilay Shroff
2026-02-15 21:18 ` Haris Iqbal
2026-02-16 0:33 ` Chaitanya Kulkarni
2026-02-23 7:44 ` Johannes Thumshirn
2026-02-25 10:15 ` Haris Iqbal
2026-02-23 17:08 ` Bart Van Assche
2026-02-25 2:55 ` Chaitanya Kulkarni
2026-02-25 10:07 ` Haris Iqbal
2026-02-25 16:29 ` Bart Van Assche [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 6:30 Chaitanya Kulkarni
2024-01-09 21:31 ` Bart Van Assche
2024-01-09 22:01 ` Chaitanya Kulkarni
2024-01-09 22:08 ` Bart Van Assche
2024-01-17 8:50 ` Daniel Wagner
2024-01-23 15:07 ` Daniel Wagner
2024-02-14 7:32 ` Shinichiro Kawasaki
2024-02-21 18:32 ` Luis Chamberlain
2024-02-22 9:31 ` Daniel Wagner
2024-02-22 15:54 ` Luis Chamberlain
2024-02-22 16:16 ` Daniel Wagner
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=4bc30e61-e83d-4368-98bd-78f7d22c3f2e@acm.org \
--to=bvanassche@acm.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=chaitanyak@nvidia.com \
--cc=dlemoal@kernel.org \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=haris.iqbal@ionos.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=javier@javigon.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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