From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org, mst@redhat.com
Cc: aliguori@us.ibm.com, gleb@redhat.com, jbaron@redhat.com,
yamahata@valinux.co.jp, alex.williamson@redhat.com,
kraxel@redhat.com, pbonzini@redhat.com, imammedo@redhat.com,
aurelien@aurel32.net
Subject: [Qemu-devel] [PATCH v2 0/5] PCI hotplug fixes/cleanup
Date: Thu, 05 Apr 2012 11:07:01 -0600 [thread overview]
Message-ID: <20120405170331.14105.52652.stgit@bling.home> (raw)
Incorporating feedback from v1. Re-ordered so first 2 patches are fixes,
allowing easier backport. Instead of declaring the eject register is
write-only we define it to be a feature bits register and define the base
feature set in the docs (a feature register seems easier to maintain than
a version register). Other patches remain the same. Thanks,
Alex
---
Alex Williamson (5):
acpi_piix4: Use pci_get/set_byte
acpi_piix4: Re-define PCI hotplug eject register read
acpi_piix4: Remove PCI_RMV_BASE write code
acpi_piix4: Fix PCI hotplug race
acpi_piix4: Disallow write to up/down PCI hotplug registers
docs/specs/acpi_pci_hotplug.txt | 18 +++-
hw/acpi_piix4.c | 180 +++++++++++++++++++++------------------
2 files changed, 109 insertions(+), 89 deletions(-)
next reply other threads:[~2012-04-05 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 17:07 Alex Williamson [this message]
2012-04-05 17:07 ` [Qemu-devel] [PATCH v2 1/5] acpi_piix4: Disallow write to up/down PCI hotplug registers Alex Williamson
2012-04-05 17:07 ` [Qemu-devel] [PATCH v2 2/5] acpi_piix4: Fix PCI hotplug race Alex Williamson
2012-04-05 17:07 ` [Qemu-devel] [PATCH v2 3/5] acpi_piix4: Remove PCI_RMV_BASE write code Alex Williamson
2012-04-05 17:07 ` [Qemu-devel] [PATCH v2 4/5] acpi_piix4: Re-define PCI hotplug eject register read Alex Williamson
2012-04-05 17:07 ` [Qemu-devel] [PATCH v2 5/5] acpi_piix4: Use pci_get/set_byte Alex Williamson
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=20120405170331.14105.52652.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=aurelien@aurel32.net \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=jbaron@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).