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

[Xen-devel] permit_access functionality

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] permit_access functionality
From: "Jayant Mangalampalli" <Jayant_Mangalampalli@xxxxxxxxxxx>
Date: Fri, 28 Sep 2007 23:19:35 +0530
Delivery-date: Fri, 28 Sep 2007 10:50:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgB9+79YBY6UD7ZSFiKca7XMphIpg==
Thread-topic: permit_access functionality
What is the exact use of ioport_permit_access() and irq_permit_access() kind of 
functions? If I permit port/irq access to HVM guest for a particular port or 
IRQ, does that mean guest VCPU does not issue a hypercall when accessing them? 
If a PIRQ is asserted by physical hardware, can hvm guest directly get 
notification if given such access?
 
Thanks
Jayant

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

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