From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60176) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S9JYa-0001Iw-0l for qemu-devel@nongnu.org; Sun, 18 Mar 2012 13:06:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S9JYY-0005sG-As for qemu-devel@nongnu.org; Sun, 18 Mar 2012 13:06:11 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42049) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S9JYY-0005rv-0t for qemu-devel@nongnu.org; Sun, 18 Mar 2012 13:06:10 -0400 Date: Sun, 18 Mar 2012 19:06:23 +0200 From: "Michael S. Tsirkin" Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] [PATCH 0/2] acpi: robust notifications List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Williamson , gleb@redhat.com, Anthony Liguori , qemu-devel@nongnu.org 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