From: Stefan Hajnoczi <stefanha@redhat.com>
To: Matthieu Rolla <matthieu@minio.io>
Cc: "\"Daniel P. Berrangé\"" <berrange@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, its@irrelevant.dk,
kbusch@kernel.org, mr-083 <matthieu@min.io>
Subject: Re: [PATCH 2/2] block/monitor: add drive_insert HMP command
Date: Thu, 16 Apr 2026 15:52:08 -0400 [thread overview]
Message-ID: <20260416195208.GB258343@fedora> (raw)
In-Reply-To: <7E17AD80-CF52-44FC-A0FE-29B481EF5B40@minio.io>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Wed, Apr 15, 2026 at 02:32:39PM +0200, Matthieu Rolla wrote:
> Thanks Daniel,
>
> It makes sense Thanks.
>
> Looking at the existing code, blockdev-insert-medium already does the backend/frontend association via blk_insert_bs(), but is restricted to removable devices.
> A new QMP command like blockdev-attach could reuse the same logic without the removable restriction, paired with blockdev-add for creating the block node.
>
> Would that be a better approach ?
Hi Matthieu,
I was wondering whether the blockdev needs to be changed at all. Since
the disk image remains the same, is it sufficient to inject the PCIe SDN
and then recover the NVMe PCI controller?
I don't understand the test scenario well enough, but it seems like
you're testing at the PCIe level here rather than nothin NVMe- or
blockdev-specific. Therefore blockdev commands may not be necessary.
If the testing can be done completely at the PCIe level then that would
also allow other device types to be tested in the same way, which would
be nice.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2026-04-16 19:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 6:01 [PATCH 0/2] NVMe namespace hotplug and drive reconnection support mr-083
2026-04-09 6:01 ` [PATCH 1/2] hw/nvme: add namespace hotplug support mr-083
2026-04-09 6:01 ` [PATCH 2/2] block/monitor: add drive_insert HMP command mr-083
2026-04-14 17:57 ` Stefan Hajnoczi
2026-04-14 18:02 ` Matthieu Rolla
2026-04-14 19:05 ` Warner Losh
2026-04-14 21:01 ` Matthieu Rolla
2026-04-15 10:48 ` Daniel P. Berrangé
2026-04-15 12:32 ` Matthieu Rolla
2026-04-16 19:52 ` Stefan Hajnoczi [this message]
2026-04-16 22:00 ` Matthieu Rolla
2026-04-15 12:33 ` Stefan Hajnoczi
2026-04-09 21:34 ` [PATCH v2] hw/nvme: add namespace hotplug support mr-083
2026-04-10 12:41 ` Stefan Hajnoczi
2026-04-10 14:30 ` [PATCH v3] " mr-083
2026-04-10 14:33 ` Matthieu Rolla
2026-04-10 20:14 ` Stefan Hajnoczi
2026-04-13 15:24 ` Matthieu Rolla
2026-04-13 17:17 ` [PATCH 0/2] NVMe namespace hotplug and drive reconnection support Klaus Jensen
2026-04-14 12:42 ` Stefan Hajnoczi
2026-04-14 13:36 ` Matthieu Rolla
2026-04-14 18:09 ` Keith Busch
2026-04-14 18:10 ` Stefan Hajnoczi
2026-04-14 18:14 ` Matthieu Rolla
2026-04-15 12:45 ` Stefan Hajnoczi
2026-04-15 17:39 ` Matthieu Rolla
2026-04-14 14:04 ` John Meneghini
2026-04-16 10:11 ` Nilay Shroff
2026-04-16 12:33 ` Matthieu Rolla
2026-04-14 14:42 ` Keith Busch
2026-04-15 17:38 ` [PATCH v4] hw/nvme: add namespace hotplug support mr-083
2026-04-16 19:42 ` Stefan Hajnoczi
2026-04-17 9:29 ` Klaus Jensen
2026-04-17 9:45 ` Matthieu Rolla
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 7:01 [PATCH 0/2] NVMe namespace hotplug and drive reconnection support mr-083
2026-04-09 7:01 ` [PATCH 2/2] block/monitor: add drive_insert HMP command mr-083
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=20260416195208.GB258343@fedora \
--to=stefanha@redhat.com \
--cc=berrange@redhat.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=matthieu@min.io \
--cc=matthieu@minio.io \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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.