From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ani Sinha <ani.sinha@nutanix.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] Add a new PIIX option to control PCI hot unplugging of devices on non-root buses
Date: Fri, 17 Apr 2020 12:09:00 -0400 [thread overview]
Message-ID: <20200417120732-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2A13ACCD-BD24-41FB-B6EA-2804F7C1FF1D@nutanix.com>
On Fri, Apr 17, 2020 at 03:36:14PM +0000, Ani Sinha wrote:
>
>
> > On Apr 17, 2020, at 8:57 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > Is there a real reason to do this? Can't we just limit the
> > hotplug control to pcie ports? At some point I'd like us to
> > start leaving piix alone..
>
> Yes we really need this feature as want to be able to hot plug devices into the guest but prevent customers from hot unplugging them from say Windows system tray.
>
> ani
Problem is, I think this is not something we can support with pcie or shpc.
I'm reluctant to add features that only ACPI can support,
we are trying to phase that out.
Better ideas?
--
MST
next prev parent reply other threads:[~2020-04-17 16:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 15:13 [PATCH] Add a new PIIX option to control PCI hot unplugging of devices on non-root buses Ani Sinha
2020-04-17 15:27 ` Michael S. Tsirkin
2020-04-17 15:36 ` Ani Sinha
2020-04-17 16:09 ` Michael S. Tsirkin [this message]
2020-04-17 16:35 ` Ani Sinha
2020-04-17 21:56 ` Laine Stump
2020-04-18 3:25 ` Ani Sinha
2020-04-18 12:48 ` Marcel Apfelbaum
2020-04-19 4:00 ` Ani Sinha
2020-04-20 15:04 ` Ani Sinha
2020-04-20 15:38 ` Ani Sinha
2020-04-20 18:35 ` Julia Suvorova
2020-04-20 9:24 ` Daniel P. Berrangé
2020-04-20 10:33 ` Ani Sinha
2020-04-20 11:40 ` Philippe Mathieu-Daudé
2020-04-20 15:02 ` Michael S. Tsirkin
2020-04-21 14:45 ` Ani Sinha
2020-04-21 15:02 ` Daniel P. Berrangé
2020-04-22 10:45 ` Ani Sinha
2020-04-24 15:23 ` Ani Sinha
2020-04-24 18:44 ` Eduardo Habkost
2020-04-27 9:06 ` Ani Sinha
2020-04-29 15:32 ` Igor Mammedov
2020-05-10 17:42 ` Ani Sinha
2020-05-11 18:54 ` Igor Mammedov
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=20200417120732-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ani.sinha@nutanix.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).