All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: Ani Sinha <ani.sinha@nutanix.com>,
	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: Mon, 20 Apr 2020 13:40:24 +0200	[thread overview]
Message-ID: <5182c28e-0a84-8141-89ca-954dacfc0ca7@redhat.com> (raw)
In-Reply-To: <20200420092459.GF346737@redhat.com>

On 4/20/20 11:24 AM, Daniel P. Berrangé wrote:
> On Fri, Apr 17, 2020 at 12:09:00PM -0400, Michael S. Tsirkin wrote:
>> 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.
> 
>  From the upstream POV, there's been no decision / agreement to phase
> out PIIX, this is purely a RHEL downstream decision & plan. If other
> distros / users have a different POV, and find the feature useful, we
> should accept the patch if it meets the normal QEMU patch requirements.

Remotely related, this thread suggest to rename the current Frankenstein 
PIIX as 'virt_southbridge' /s
https://www.mail-archive.com/qemu-devel@nongnu.org/msg691232.html

Seriously, apparently thinking to modify PIIX scares various people.
Is there a virt equivalent that could work?
On one hand people want to use Windows guest unmodified (or with 
digitally signed drivers, which seems impossible to do with virtio 
package [*]). OTOH we are not sure how the PIIX model works because it 
is not based on specs, and does not match its datasheet, and do not want 
to modify it.

[*] If you click on 'How to Release-Sign File System Drivers' on
https://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers
it opens https://www.microsoft.com/whdc/driver/tips/IFS_Signing.mspx
and displays "Your request has been blocked."...

> 
> Regards,
> Daniel
> 



  parent reply	other threads:[~2020-04-20 11:41 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
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é [this message]
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=5182c28e-0a84-8141-89ca-954dacfc0ca7@redhat.com \
    --to=philmd@redhat.com \
    --cc=ani.sinha@nutanix.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@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 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.