From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
gleb@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] acpi: robust notifications
Date: Sun, 18 Mar 2012 19:06:23 +0200 [thread overview]
Message-ID: <cover.1332089914.git.mst@redhat.com> (raw)
acpi currently clears up/down registers on each hotplug
request. This loses events if they are done quickly.
It's easy to clear down on ej write.
To detect that guest was notified of device addition,
we track configuration accesses since system reset.
Michael S. Tsirkin (2):
pci: track function accesses
acpi: don't clear up/down on each host change
hw/acpi_piix4.c | 32 +++++++++++++++++++++++++++-----
hw/pci.c | 26 ++++++++++++++++++++++++++
hw/pci.h | 3 +++
hw/pci_host.c | 2 ++
4 files changed, 58 insertions(+), 5 deletions(-)
--
1.7.9.111.gf3fb0
next reply other threads:[~2012-03-18 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 17:06 Michael S. Tsirkin [this message]
2012-03-18 17:06 ` [Qemu-devel] [PATCH 1/2] pci: track function accesses Michael S. Tsirkin
2012-03-18 17:06 ` [Qemu-devel] [PATCH 2/2] acpi: don't clear up/down on each host change Michael S. Tsirkin
2012-03-19 8:28 ` [Qemu-devel] [PATCH 0/2] acpi: robust notifications 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=cover.1332089914.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=gleb@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).