[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: Thu, 7 Dec 2006 11:03:31 +0800
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 06 Dec 2006 19:04:05 -0800
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AccZqJ3QBZFobdmcSVOcKcmHo7fNtwAAvluA
  • Thread-topic: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism

Doi.Tsunehisa@xxxxxxxxxxxxxx write on 2006年12月7日 10:37:
> Hi Anthony,
>   I've thought that we can get GSI for platform_pci from Device ID
> in HV, if mapping betweeen devid and gsi is fixed.
> 
>   There is hvm_pci_intx_gsi() macro in xen/arch/ia64/vmx/viosapic.c
> 
> [xen/arch/ia64/vmx/viosapic.c]-------------------------------------
> #define hvm_pci_intx_gsi(dev, intx)  \
>     (((((dev) << 2) + ((dev) >> 3) + (intx)) & 31) + 16)
> 
> 
> void viosapic_set_pci_irq(struct domain *d, int device, int intx, int
> level) {
>     int irq;
>     irq = hvm_pci_intx_gsi(device, intx);
> 
>     viosapic_set_irq(d, irq, level);
> }
> -------------------------------------------------------------------
> 
>   It seems that device to gsi mapping is fixed. If it's correct,
> we can get GSI in HV from device ID which is notified from PV-driver
> with set_callback_irq.
> 
>   What do you think about this ?

That's a good solution for IPF side.

It may not work for IA32 side, if apic is disable.

So we can use #ifdef.

Anthony

> 
> Thanks,
> - 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®.