Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] PV drivers for HVM guest

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ky Srinivasan" <KSrinivasan.PRV-5.PROVO@xxxxxxxxxx>
Subject: Re: [Xen-devel] PV drivers for HVM guest
From: "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx>
Date: Fri, 27 Apr 2007 14:40:50 -0600
Delivery-date: Fri, 27 Apr 2007 13:39:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4632028C.E57C.0030.0@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/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>
References: <4632028C.E57C.0030.0@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
After some more hacking, if I were to use the irqline information available in 
the pci config space for this device, both in establishing the handler  for 
this device (request_irq()) as well as in registering the callback irq 
(set_callback_irq()) things seem to work.

Regards,

K. Y


>>> On Fri, Apr 27, 2007 at  3:12 PM, in message 
>>> <4632028C.E57C.0030.0@xxxxxxxxxx>,
"Ky Srinivasan" <ksrinivasan@xxxxxxxxxx> wrote: 
> In platform_pci.c we register the IRQ that the hypervisor should use to 
> notify the guest in response to event channel notifications.  In cases where 
> the mapping between irq and vectors are not one to one, I am not sure how 
> this can work. For instance, on a  RHEL 4 installation (with acpi turned on)  
> I am looking at, the irq assigned to the platform- pci device is 185! 
> Consequently the set_callback_irq() fails since the number passed down 
> exceeds the number of pins being emulated. Any insight will be greatly 
> appreciated.
> 
> Regards,
> 
> K. Y
> 
> 
> 
> _______________________________________________
> Xen- devel mailing list
> Xen- devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen- devel



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

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