qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: Damien Hedde <dhedde@kalrayinc.com>
Cc: qemu-block@nongnu.org, Keith Busch <kbusch@kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Titouan Huard <thuard@kalrayinc.com>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: NVME hotplug support ?
Date: Tue, 23 Jan 2024 12:15:56 +0100	[thread overview]
Message-ID: <Za-f7Mp8RnBiynZ0@cormorant.local> (raw)
In-Reply-To: <PR2P264MB0861AAF89D0B361A33710261D1742@PR2P264MB0861.FRAP264.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]

On Jan 23 10:59, Damien Hedde wrote:
> Hi all,
> 
> We are currently looking into hotplugging nvme devices and it is currently not possible:
> When nvme was introduced 2 years ago, the feature was disabled.
> > commit cc6fb6bc506e6c47ed604fcb7b7413dff0b7d845
> > Author: Klaus Jensen 
> > Date:   Tue Jul 6 10:48:40 2021 +0200
> >
> >    hw/nvme: mark nvme-subsys non-hotpluggable
> >    
> >    We currently lack the infrastructure to handle subsystem hotplugging, so
> >    disable it.
> 
> Do someone know what's lacking or anyone have some tips/idea of what we should develop to add the support ?
> 
> Regards,
> --
> Damien 
> 

That's not entirely true.

The *subsystem* is non-hotpluggable, but individual controllers can be
hotplugged. Even into an existing subsystem.

However, you cannot hotplug pci devices unless you set up a pcie root
port. Say,

  -device "pcie-root-port,id=pcie_root_port0,chassis=1,slot=0"
  -device "nvme,id=nvme0,serial=nvme0,bus=pcie_root_port0"

nvme0 can then be removed with device_del and added back as a new device
with device_add.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-01-23 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 10:59 NVME hotplug support ? Damien Hedde
2024-01-23 11:15 ` Klaus Jensen [this message]
2024-01-23 12:40 ` Hannes Reinecke
2024-01-24  6:52   ` Philippe Mathieu-Daudé
2024-01-24  7:47     ` Hannes Reinecke
2024-01-29 13:13       ` Damien Hedde
2024-01-29 13:37         ` Klaus Jensen
2024-01-29 15:35         ` Hannes Reinecke
2024-02-05 13:33           ` Damien Hedde
2024-01-24  7:39   ` Klaus Jensen

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=Za-f7Mp8RnBiynZ0@cormorant.local \
    --to=its@irrelevant.dk \
    --cc=dhedde@kalrayinc.com \
    --cc=hare@suse.de \
    --cc=kbusch@kernel.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuard@kalrayinc.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;
as well as URLs for NNTP newsgroup(s).