qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Bruce Rogers <brogers@suse.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: [Qemu-devel] [PULL 8/9] ACPI: don't call acpi_pcihp_device_plug_cb on xen
Date: Wed, 10 May 2017 22:08:32 +0300	[thread overview]
Message-ID: <1494443192-17177-9-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1494443192-17177-1-git-send-email-mst@redhat.com>

From: Bruce Rogers <brogers@suse.com>

Commit f0c9d64a exposed the issue that with a xenfv machine using
pci passthrough, acpi pci hotplug code was being executed by mistake.
Guard calls to acpi_pcihp_device_plug_cb (and corresponding
acpi_pcihp_device_unplug_cb) with a check for xen_enabled(). Without
this check I am seeing an error that the bus doesn't have the
acpi-pcihp-bsel property set.

Signed-off-by: Bruce Rogers <brogers@suse.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 hw/acpi/piix4.c | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/hw/acpi/piix4.c b/hw/acpi/piix4.c
index a553a7e..c409374 100644
--- a/hw/acpi/piix4.c
+++ b/hw/acpi/piix4.c
@@ -385,7 +385,10 @@ static void piix4_device_plug_cb(HotplugHandler *hotplug_dev,
                                 dev, errp);
         }
     } else if (object_dynamic_cast(OBJECT(dev), TYPE_PCI_DEVICE)) {
-        acpi_pcihp_device_plug_cb(hotplug_dev, &s->acpi_pci_hotplug, dev, errp);
+        if (!xen_enabled()) {
+            acpi_pcihp_device_plug_cb(hotplug_dev, &s->acpi_pci_hotplug, dev,
+                                      errp);
+        }
     } else if (object_dynamic_cast(OBJECT(dev), TYPE_CPU)) {
         if (s->cpu_hotplug_legacy) {
             legacy_acpi_cpu_plug_cb(hotplug_dev, &s->gpe_cpu, dev, errp);
@@ -408,8 +411,10 @@ static void piix4_device_unplug_request_cb(HotplugHandler *hotplug_dev,
         acpi_memory_unplug_request_cb(hotplug_dev, &s->acpi_memory_hotplug,
                                       dev, errp);
     } else if (object_dynamic_cast(OBJECT(dev), TYPE_PCI_DEVICE)) {
-        acpi_pcihp_device_unplug_cb(hotplug_dev, &s->acpi_pci_hotplug, dev,
-                                    errp);
+        if (!xen_enabled()) {
+            acpi_pcihp_device_unplug_cb(hotplug_dev, &s->acpi_pci_hotplug, dev,
+                                        errp);
+        }
     } else if (object_dynamic_cast(OBJECT(dev), TYPE_CPU) &&
                !s->cpu_hotplug_legacy) {
         acpi_cpu_unplug_request_cb(hotplug_dev, &s->cpuhp_state, dev, errp);
-- 
MST

  parent reply	other threads:[~2017-05-10 19:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 19:07 [Qemu-devel] [PULL 0/9] pci, virtio, vhost: fixes Michael S. Tsirkin
2017-05-10 19:07 ` [Qemu-devel] [PULL 1/9] hw/acpi-defs: replace leading X with x_ in FADT field names Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 2/9] hw/arm/virt: generate 64-bit addressable ACPI objects Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 3/9] hw/virtio: fix vhost user fails to startup when MQ Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 4/9] libvhost-user: fix crash when rings aren't ready Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 5/9] pc/fwcfg: unbreak migration from qemu-2.5 and qemu-2.6 during firmware boot Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 6/9] pc: add 2.10 machine type Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 7/9] iommu: Don't crash if machine is not PC_MACHINE Michael S. Tsirkin
2017-05-10 19:08 ` Michael S. Tsirkin [this message]
2017-05-10 19:08 ` [Qemu-devel] [PULL 9/9] acpi-defs: clean up open brace usage Michael S. Tsirkin
2017-05-10 19:48 ` [Qemu-devel] [PULL 0/9] pci, virtio, vhost: fixes no-reply
2017-05-15 12:58 ` Stefan Hajnoczi
2017-05-15 13:04   ` Michael S. Tsirkin
2017-05-17 21:40     ` Michael S. Tsirkin
2017-05-18  9:02       ` Stefan Hajnoczi
2017-05-18  9:02 ` Stefan Hajnoczi

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=1494443192-17177-9-git-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=brogers@suse.com \
    --cc=imammedo@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).