From: "Michael S. Tsirkin" <mst@redhat.com>
To: Julia Suvorova <jusual@redhat.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org,
Laine Stump <laine@redhat.com>
Subject: Re: Disabling PCI "hot-unplug" for a guest (and/or a single PCI device)
Date: Tue, 4 Feb 2020 11:35:37 -0500 [thread overview]
Message-ID: <20200204113457-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAMDeoFVkoTZSQ=PV=mc_AGoZ445Wug4F+RV5utaYb+jhPEtkJg@mail.gmail.com>
On Tue, Feb 04, 2020 at 05:13:54PM +0100, Julia Suvorova wrote:
> On Tue, Feb 4, 2020 at 11:26 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Mon, Feb 03, 2020 at 05:19:51PM -0500, Laine Stump wrote:
> > > 3) qemu could add a "hotpluggable=no" commandline option to all PCI devices
> > > (including vfio-pci) and then do whatever is necessary to make sure this is
> > > honored in the emulated hardware (is it possible to set this on a per-slot
> > > basis in a PCI controller? Or must it be done for an entire controller?
> >
> > I think it's possible on a per-slot basis, yes.
>
> There's a "Hot-Plug Capable" option in Slot Capability register, so we
> can switch it off. But it's only for pcie devices, can't say anything
> about conventional pci.
>
> Best regards, Julia Suvorova.
For conventional PCI, we can drop SHPC capability and remove
the eject method from ACPI.
next prev parent reply other threads:[~2020-02-04 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 22:19 Disabling PCI "hot-unplug" for a guest (and/or a single PCI device) Laine Stump
2020-02-04 10:24 ` Michael S. Tsirkin
2020-02-04 16:13 ` Julia Suvorova
2020-02-04 16:35 ` Michael S. Tsirkin [this message]
2020-02-05 11:36 ` Daniel P. Berrangé
2020-02-05 13:10 ` Michael S. Tsirkin
2020-02-04 18:43 ` Daniel P. Berrangé
2020-02-05 16:29 ` Laine Stump
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=20200204113457-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jusual@redhat.com \
--cc=laine@redhat.com \
--cc=libvir-list@redhat.com \
--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 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).