[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism


  • To: <Doi.Tsunehisa@xxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Wed, 6 Dec 2006 10:18:22 +0800
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 05 Dec 2006 18:18:32 -0800
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AccYZkhS8ZXC/PTfQzWKW7drqOlQAQAdbFow
  • Thread-topic: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism

Doi.Tsunehisa@xxxxxxxxxxxxxx write on 2006年12月5日 19:59:
> 
>   Hardware IRQ is equal to GSI, but the IRQ in IPF-linux world is
> abstruct value not GSI. So we need to get GSI for platform-pci from
> IPF-linux world's IRQ. But I didn't find it.
> 
 * Hypervisor becomes to be able to use both GSI and Vector for callback
    irq.
    - For example, if it is normal value, HV accepts it as GSI.
      If it is value which is set MSB, HV accepts it as Vector.
  * If hypervisor gets Vector as callback irq, hypervisor finds the GSI
    for the pseudo device from virtual interrupt controller setting.

Hi Doi,

Understand you question now.

Linux-irq is equal to vector in VIOSAPIC,

I think linux-irq will not alter after guest linux boot,
So platform_pci can call set_callback_irq using vector (linux-irq).
HV will directly pend this vector without looking for VIOSAPIC.


Anthony.


> 
> - Tsunehisa Doi

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.