From: Eduardo Habkost <ehabkost@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Ani Sinha" <ani.sinha@nutanix.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Marcel Apfelbaum" <marcel@redhat.com>,
"Paolo Bonzini" <pbonzini@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, 24 Apr 2020 14:44:48 -0400 [thread overview]
Message-ID: <20200424184448.GS4952@habkost.net> (raw)
In-Reply-To: <819DA747-F897-44A4-A238-B6F20C4C8B08@nutanix.com>
On Fri, Apr 24, 2020 at 03:23:56PM +0000, Ani Sinha wrote:
>
>
> > On Apr 22, 2020, at 4:15 PM, Ani Sinha <ani.sinha@nutanix.com> wrote:
> >
> >
> >
> >> On Apr 21, 2020, at 8:32 PM, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >>
> >> On Tue, Apr 21, 2020 at 02:45:04PM +0000, Ani Sinha wrote:
> >>>
> >>>
> >>>> On Apr 20, 2020, at 8:32 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> >>>>
> >>>> But I for one would like to focus on keeping PIIX stable
> >>>> and focus development on q35. Not bloating PIIX with lots of new
> >>>> features is IMHO a good way to do that.
> >>>
> >>> Does this mean this patch is a no-go then? :(
> >>
> >> I'd support this patch, as I don't think it can really be described as
> >> bloat or destabalizing. It is just adding a simple property to
> >> conditionalize existing functionality. Telling people to switch to Q35
> >> is unreasonable as it is not a simple 1-1 conversion from existing use
> >> of PIIX. Q35 has much higher complexity in its configuration, has higher
> >> memory overhead per VM too, and lacks certain features of PIIX too.
> >
> > Cool. How do we go forward from here?
> >
>
> We would really appreciate if we can add this extra knob in
> Qemu. Maybe someone else also in the community will find this
> useful. We don’t want to maintain this patch internally forever
> but rather prefer we maintain this as a Qemu community.
Michael, I agree with Daniel here and I don't think we should
start refusing PIIX features if they are useful for a portion of
the QEMU community.
Would you reconsider and merge this patch?
--
Eduardo
next prev parent reply other threads:[~2020-04-24 18:46 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é
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 [this message]
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=20200424184448.GS4952@habkost.net \
--to=ehabkost@redhat.com \
--cc=ani.sinha@nutanix.com \
--cc=berrange@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.