WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] ACPI fixed event or General Purpose Event to HVM guest.

To: "Bill Rieske" <brieske@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] ACPI fixed event or General Purpose Event to HVM guest.
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 17 Jul 2008 09:10:35 +0800
Cc:
Delivery-date: Wed, 16 Jul 2008 18:11:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <487E1D6B.D34E.008B.3@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <487E1D6B.D34E.008B.3@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjnjqXmS/u6C5pAQkuYnNimc4474gAGIIFw
Thread-topic: [Xen-devel] ACPI fixed event or General Purpose Event to HVM guest.
>From:Bill Rieske
>Sent: 2008年7月17日 5:55
>
>Has there been any work done on getting an ACPI fixed event or 
>perhaps a general
>purpose event delivered to an HVM guest.  Whereby, the HVM 
>guests OSPM could consume the event and act accordingly.

Now Xen support live migration with VT-d assigned device, which 
is based on a virtual ACPI hotplug mechanism, where one specific
GPE bit is created within Qemu. You can check piix4acpi.c in
Qemu for reference.

>
>Or Perhaps better stated how would one go about passing an 
>ACPI fixed event or general purpose event that was raised and 
>consumed by dom0 and subsequently pass the event on to each of 
>the HVM domu's.  
>

But if you're talking about passing through a physical ACPI event
to HVM, it seems a bit tricky since not all ACPI events are 
waterfalled to user space, and even when some does, it doesn't 
make sense to simply forward already-consumed event to HVM,
as Qemu ACPI table is different from physical one. 

So, what's your main purpose here?

Thanks,
Kevin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>