From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
mtosatti@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
gleb@redhat.com
Subject: [Qemu-devel] [PATCH] acpi: beginnings of piix acpi interface doc
Date: Mon, 12 Mar 2012 11:35:29 +0200 [thread overview]
Message-ID: <20120312093510.GA32194@redhat.com> (raw)
Before we start tweaking and enhancing hardware, I think
it makes sense to document what we currently have, to make
sure we stay compatible.
This documents the hotplug interface for piix.
Stubs for cpu hotplug, PM.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
docs/acpi.txt | 32 ++++++++++++++++++++++++++++++++
1 files changed, 32 insertions(+), 0 deletions(-)
create mode 100644 docs/acpi.txt
diff --git a/docs/acpi.txt b/docs/acpi.txt
new file mode 100644
index 0000000..4938d48
--- /dev/null
+++ b/docs/acpi.txt
@@ -0,0 +1,32 @@
+QEMU exposes the following registers to guests,
+intended primarily for use by the ACPI interface.
+
+PCI Hotplug
+----
+
+Events use the standard GPE register:
+GPE 0xafe0 - an ACPI GPE register
+
+Hotplug events set GPE bit 1 (mask 0x2)
+
+The following registers are used for PCI hotplug.
+Each register is 32 bit (4 bytes) long, and has little endian format.
+Bits 0-31 in each register correspond to slots 0-31 on the root bus,
+respectively.
+
+UP 0xae00 - RO - Bit set by host on device insertion (note:existing implementations
+ trigger device check event)
+DOWN 0xae04 - RO - Bit set by host on user eject request
+EJ0 0xae08 - WO - Bit set by guest removes all power to device
+RMV 0xae0c - RO - Bit set by host if slot supports hotplug
+ (can not change while guest is up)
+
+
+Power management
+----
+TODO
+
+
+CPU hotplug
+----
+TODO
--
1.7.9.111.gf3fb0
next reply other threads:[~2012-03-12 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 9:35 Michael S. Tsirkin [this message]
2012-03-12 11:14 ` [Qemu-devel] [PATCH] acpi: beginnings of piix acpi interface doc Gleb Natapov
2012-03-12 13:24 ` Michael S. Tsirkin
2012-03-12 13:25 ` 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=20120312093510.GA32194@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=gleb@redhat.com \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.