From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, ddutile@redhat.com, gleb@redhat.com,
mst@redhat.com
Subject: [Qemu-devel] [PATCH 4/6] acpi_piix4: Track PCI hotplug status and allow non-ACPI remove path
Date: Tue, 06 Mar 2012 17:14:51 -0700 [thread overview]
Message-ID: <20120307001438.3079.32280.stgit@bling.home> (raw)
In-Reply-To: <20120307000340.3079.87515.stgit@bling.home>
When a guest probes a device, clear the "up" bit in the hotplug
register. This allows us to enable a non-ACPI remove path for
devices added, but never accessed by the guest. This is useful
when a guest does not have ACPI PCI hotplug support to avoid losing
devices to a guest. We also now individually track bits for "up"
and "down" rather than clearing both on each PCI hotplug action.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
hw/acpi_piix4.c | 58 ++++++++++++++++++++++++++++++++++++++++++++-----------
1 files changed, 46 insertions(+), 12 deletions(-)
diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
index 4d88e23..7e766e5 100644
--- a/hw/acpi_piix4.c
+++ b/hw/acpi_piix4.c
@@ -27,6 +27,7 @@
#include "sysemu.h"
#include "range.h"
#include "ioport.h"
+#include "pci_host.h"
//#define DEBUG
@@ -75,6 +76,7 @@ typedef struct PIIX4PMState {
qemu_irq smi_irq;
int kvm_enabled;
Notifier machine_ready;
+ Notifier device_probe;
/* for pci hotplug */
ACPIGPE gpe;
@@ -336,6 +338,16 @@ static void piix4_pm_machine_ready(Notifier *n, void *opaque)
}
+static void piix4_pm_device_probe(Notifier *n, void *opaque)
+{
+ PIIX4PMState *s = container_of(n, PIIX4PMState, device_probe);
+ PCIDevice *pdev = opaque;
+
+ if (pci_find_domain(pdev->bus) == 0 && pci_bus_num(pdev->bus) == 0) {
+ s->pci0_status.up &= ~(1U << PCI_SLOT(pdev->devfn));
+ }
+}
+
static PIIX4PMState *global_piix4_pm_state; /* cpu hotadd */
static int piix4_pm_initfn(PCIDevice *dev)
@@ -383,6 +395,8 @@ static int piix4_pm_initfn(PCIDevice *dev)
qemu_add_machine_init_done_notifier(&s->machine_ready);
qemu_register_reset(piix4_reset, s);
piix4_acpi_system_hot_add_init(dev->bus, s);
+ s->device_probe.notify = piix4_pm_device_probe;
+ pci_host_add_dev_probe_notifier(&s->device_probe);
return 0;
}
@@ -502,6 +516,7 @@ static void pciej_write(void *opaque, uint32_t addr, uint32_t val)
PCIDeviceClass *pc = PCI_DEVICE_GET_CLASS(dev);
if (PCI_SLOT(dev->devfn) == slot && !pc->no_hotplug) {
qdev_free(qdev);
+ s->pci0_status.down &= ~(1U << slot);
}
}
@@ -594,16 +609,41 @@ void qemu_system_cpu_hot_add(int cpu, int state)
}
#endif
-static void enable_device(PIIX4PMState *s, int slot)
+static int enable_device(PIIX4PMState *s, int slot)
{
+ uint32_t mask = 1U << slot;
+
+ if ((s->pci0_status.up | s->pci0_status.down) & mask) {
+ return -1;
+ }
+
s->gpe.sts[0] |= PIIX4_PCI_HOTPLUG_STATUS;
- s->pci0_status.up |= (1 << slot);
+ s->pci0_status.up |= mask;
+
+ pm_update_sci(s);
+ return 0;
}
-static void disable_device(PIIX4PMState *s, int slot)
+static int disable_device(PIIX4PMState *s, int slot)
{
+ uint32_t mask = 1U << slot;
+
+ if (s->pci0_status.up & mask) {
+ s->pci0_status.up &= ~mask;
+ pciej_write(s, PCI_EJ_BASE, mask);
+
+ /* Clear GPE PCI hotplug status if nothing left pending */
+ if (!(s->pci0_status.up | s->pci0_status.down)) {
+ s->gpe.sts[0] &= ~PIIX4_PCI_HOTPLUG_STATUS;
+ }
+ return 0;
+ }
+
s->gpe.sts[0] |= PIIX4_PCI_HOTPLUG_STATUS;
- s->pci0_status.down |= (1 << slot);
+ s->pci0_status.down |= mask;
+
+ pm_update_sci(s);
+ return 0;
}
static int piix4_device_hotplug(DeviceState *qdev, PCIDevice *dev,
@@ -620,15 +660,9 @@ static int piix4_device_hotplug(DeviceState *qdev, PCIDevice *dev,
return 0;
}
- s->pci0_status.up = 0;
- s->pci0_status.down = 0;
if (state == PCI_HOTPLUG_ENABLED) {
- enable_device(s, slot);
+ return enable_device(s, slot);
} else {
- disable_device(s, slot);
+ return disable_device(s, slot);
}
-
- pm_update_sci(s);
-
- return 0;
}
next prev parent reply other threads:[~2012-03-07 0:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 0:13 [Qemu-devel] [PATCH 0/6] PCI hotplug improvements Alex Williamson
2012-03-07 0:13 ` [Qemu-devel] [PATCH 1/6] acpi_piix4: Disallow write to up/down PCI hotplug registers Alex Williamson
2012-03-07 0:14 ` [Qemu-devel] [PATCH 2/6] acpi_piix4: Only allow writes to PCI hotplug eject register Alex Williamson
2012-03-07 0:14 ` [Qemu-devel] [PATCH 3/6] pci: Add notifier for device probing Alex Williamson
2012-03-07 9:19 ` Paolo Bonzini
2012-03-07 20:12 ` Alex Williamson
2012-03-07 0:14 ` Alex Williamson [this message]
2012-03-11 21:57 ` [Qemu-devel] [PATCH 4/6] acpi_piix4: Track PCI hotplug status and allow non-ACPI remove path Michael S. Tsirkin
2012-03-07 0:15 ` [Qemu-devel] [PATCH 5/6] acpi_piix4: Use pci_get/set_byte Alex Williamson
2012-03-07 0:15 ` [Qemu-devel] [PATCH 6/6] api_piix4: Remove PCI_RMV_BASE write code Alex Williamson
2012-03-07 12:43 ` [Qemu-devel] [PATCH 0/6] PCI hotplug improvements Gleb Natapov
2012-03-07 17:20 ` Alex Williamson
2012-03-07 18:59 ` Gleb Natapov
2012-03-07 19:51 ` Alex Williamson
2012-03-07 21:00 ` Gleb Natapov
2012-03-07 21:44 ` Alex Williamson
2012-03-07 22:17 ` Gleb Natapov
2012-03-07 22:46 ` Alex Williamson
2012-03-08 12:39 ` Gleb Natapov
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=20120307001438.3079.32280.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=ddutile@redhat.com \
--cc=gleb@redhat.com \
--cc=mst@redhat.com \
--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).