From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [RfC PATCH 0/3] q35: acpi hotplug
Date: Wed, 9 Jan 2013 16:41:34 +0100 [thread overview]
Message-ID: <1357746097-23338-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Experimental and untested patch series to implement acpi-based pci
hotplug on q35. I'm only looking for comments on the approach taken,
especially on patch #3.
The actual hotplug protocol is identical to piix, the difference is
how the io ports are mapped. piix has magic io ports at a fixed
address. For ich9 I don't want to do the same and create a pci device
instead, so the io ports show up as usual in the guests ressource
management and we can be sure we don't get conflicts.
No seabios bits yet. Should be largely identical to the piix ones,
except that we create the OperationalRegion using PciBarTarget instead
of SystemIO.
cheers,
Gerd
Gerd Hoffmann (3):
split acpi pci hotplug code into separate file
fix off-byone in hw/acpi_pci_hotplug.h
q35: add & windup ich9-pci-hotplug device
hw/Makefile.objs | 2 +-
hw/acpi_ich9.c | 89 ++++++++++++++++++++
hw/acpi_ich9.h | 1 +
hw/acpi_pci_hotplug.c | 214 +++++++++++++++++++++++++++++++++++++++++++++++++
hw/acpi_pci_hotplug.h | 26 ++++++
hw/acpi_piix4.c | 202 ++--------------------------------------------
hw/lpc_ich9.c | 5 +-
7 files changed, 344 insertions(+), 195 deletions(-)
create mode 100644 hw/acpi_pci_hotplug.c
create mode 100644 hw/acpi_pci_hotplug.h
next reply other threads:[~2013-01-09 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 15:41 Gerd Hoffmann [this message]
2013-01-09 15:41 ` [Qemu-devel] [PATCH 1/3] split acpi pci hotplug code into separate file Gerd Hoffmann
2013-01-09 21:13 ` Blue Swirl
2013-01-09 15:41 ` [Qemu-devel] [PATCH 2/3] fix off-byone in hw/acpi_pci_hotplug.h Gerd Hoffmann
2013-01-09 15:41 ` [Qemu-devel] [PATCH 3/3] q35: add & windup ich9-pci-hotplug device Gerd Hoffmann
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=1357746097-23338-1-git-send-email-kraxel@redhat.com \
--to=kraxel@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).