From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ani Sinha <ani@anisinha.ca>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Julia Suvorova <jusual@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v3] i440fx/acpi: do not add hotplug related amls for cold plugged bridges
Date: Fri, 11 Sep 2020 12:08:55 -0400 [thread overview]
Message-ID: <20200911120838-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAARzgwyKccWaPDSwsAg7bW7=F7DxAsf7Lw=TvqOkp_i6tdXZow@mail.gmail.com>
On Fri, Sep 11, 2020 at 09:35:42PM +0530, Ani Sinha wrote:
> On Fri, Sep 11, 2020 at 9:22 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Thu, Sep 10, 2020 at 12:19:19AM +0530, Ani Sinha wrote:
> > > On Sep 10, 2020, 00:00 +0530, Ani Sinha <ani@anisinha.ca>, wrote:
> > >
> > > On Sep 9, 2020, 23:20 +0530, Julia Suvorova <jusual@redhat.com>, wrote:
> > >
> > > On Fri, Sep 4, 2020 at 6:10 PM Ani Sinha <ani@anisinha.ca> wrote:
> > >
> > >
> > >
> > > Cold plugged bridges are not hot unpluggable, even when their
> > > hotplug
> > >
> > > property (acpi-pci-hotplug-with-bridge-support) is turned off.
> > > Please see
> > >
> > > the function acpi_pcihp_pc_no_hotplug() (thanks Julia). However,
> > > with
> > >
> > > the current implementaton, windows would try to hot-unplug a pci
> > > bridge when
> > >
> > > it's hotplug switch is off. This is regardless of whether there are
> > > devices
> > >
> > > attached to the bridge. This is because we add amls like _EJ0 etc
> > > for the
> > >
> > > pci slot where the bridge is cold plugged. We have a demo video
> > > here:
> > >
> > > https://youtu.be/pME2sjyQweo
> > >
> > >
> > >
> > > In this fix, we identify a cold plugged bridge and for cold plugged
> > > bridges,
> > >
> > > we do not add the appropriate amls and acpi methods that are used
> > > by the OS
> > >
> > > to identify a hot-pluggable/unpluggable pci device. After this
> > > change, Windows
> > >
> > > does not show an option to eject the PCI bridge. A demo video is
> > > here:
> > >
> > > https://youtu.be/kbgej5B9Hgs
> > >
> > >
> > >
> > > While at it, I have also updated a stale comment.
> > >
> > >
> > >
> > > This change is tested with a Windows 2012R2 guest image and Windows
> > > 2019 server
> > >
> > > guest image running on Ubuntu 18.04 host. This change is based off
> > > of upstream
> > >
> > > qemu master branch tag v5.1.0.
> > >
> > >
> > >
> > > Signed-off-by: Ani Sinha <ani@anisinha.ca>
> > >
> > >
> > >
> > > Reviewed-by: Julia Suvorova <jusual@redhat.com>
> > >
> > >
> > >
> > > BTW, aren't all bridges handled in build_append_pci_bus_devices()
> > > cold-plugged?
> > >
> > >
> > >
> > > Yes they are.
> > >
> > >
> > > Maybe as an improvement we can simply identify a bridge instead of a cold
> > > plugged bridge. However let’s have that improvement as a separate patch on top
> > > of this. Also let’s see what Igor thinks.
> >
> > Well this changes acpi tables so I don't see how this will pass
> > the unit tests. Did you test this change?
>
> There were no unit tests to cover this bridge flag. I have added the
> unit tests. It's the same one you have queued.
Hmm. somehow the new tests fail for me ...
> >
> >
> > >
> > >
> > >
> > > ---
> > >
> > > hw/i386/acpi-build.c | 12 ++++++------
> > >
> > > 1 file changed, 6 insertions(+), 6 deletions(-)
> > >
> > >
> > >
> > > changelog:
> > >
> > > v3: commit log updates providing more accurate information as
> > > received from Julia.
> > >
> > > v2: cosmetic commit log updates with patch testing information.
> > >
> > > v1: initial patch.
> > >
> > >
> > >
> > >
> > >
> > > diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> > >
> > > index b7bcbbbb2a..90b863f4ec 100644
> > >
> > > --- a/hw/i386/acpi-build.c
> > >
> > > +++ b/hw/i386/acpi-build.c
> > >
> > > @@ -359,6 +359,7 @@ static void build_append_pci_bus_devices(Aml
> > > *parent_scope, PCIBus *bus,
> > >
> > > int slot = PCI_SLOT(i);
> > >
> > > bool hotplug_enabled_dev;
> > >
> > > bool bridge_in_acpi;
> > >
> > > + bool cold_plugged_bridge;
> > >
> > >
> > >
> > > if (!pdev) {
> > >
> > > if (bsel) { /* add hotplug slots for non present devices */
> > >
> > > @@ -380,15 +381,14 @@ static void build_append_pci_bus_devices(Aml
> > > *parent_scope, PCIBus *bus,
> > >
> > > pc = PCI_DEVICE_GET_CLASS(pdev);
> > >
> > > dc = DEVICE_GET_CLASS(pdev);
> > >
> > >
> > >
> > > - /* When hotplug for bridges is enabled, bridges are
> > >
> > > - * described in ACPI separately (see build_pci_bus_end).
> > >
> > > - * In this case they aren't themselves hot-pluggable.
> > >
> > > + /*
> > >
> > > + * Cold plugged bridges aren't themselves hot-pluggable.
> > >
> > > * Hotplugged bridges *are* hot-pluggable.
> > >
> > > */
> > >
> > > - bridge_in_acpi = pc->is_bridge && pcihp_bridge_en &&
> > >
> > > - !DEVICE(pdev)->hotplugged;
> > >
> > > + cold_plugged_bridge = pc->is_bridge && !DEVICE(pdev)->hotplugged;
> > >
> > > + bridge_in_acpi = cold_plugged_bridge && pcihp_bridge_en;
> > >
> > >
> > >
> > > - hotplug_enabled_dev = bsel && dc->hotpluggable && !
> > > bridge_in_acpi;
> > >
> > > + hotplug_enabled_dev = bsel && dc->hotpluggable && !
> > > cold_plugged_bridge;
> > >
> > >
> > >
> > > if (pc->class_id == PCI_CLASS_BRIDGE_ISA) {
> > >
> > > continue;
> > >
> > > --
> > >
> > > 2.17.1
> > >
> > >
> > >
> > >
> > >
> >
next prev parent reply other threads:[~2020-09-11 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 16:10 [PATCH v3] i440fx/acpi: do not add hotplug related amls for cold plugged bridges Ani Sinha
2020-09-07 13:17 ` Ani Sinha
2020-09-09 12:14 ` Ani Sinha
2020-09-09 17:50 ` Julia Suvorova
2020-09-09 18:30 ` Ani Sinha
2020-09-09 18:49 ` Ani Sinha
2020-09-11 15:52 ` Michael S. Tsirkin
2020-09-11 16:05 ` Ani Sinha
2020-09-11 16:08 ` Michael S. Tsirkin [this message]
2020-09-11 16:15 ` Ani Sinha
2020-09-11 16:17 ` Ani Sinha
2020-09-11 18:10 ` Ani Sinha
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=20200911120838-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ani@anisinha.ca \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@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).