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

[Xen-devel] Re: [PATCH] bind passthroug pci device interrupt pins to INTA


  • To: "He, Qing" <qing.he@xxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 20 May 2008 09:54:46 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 20 May 2008 01:55:23 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aci6Mr/R/n520XTdTZqyrk6Z5fIzOwAJGc7y
  • Thread-topic: [PATCH] bind passthroug pci device interrupt pins to INTA



On 20/5/08 05:34, "He, Qing" <qing.he@xxxxxxxxx> wrote:

> The original scheme is to use the interrupt pin in the physical pci
> configuration space. However, the use of interrupt pins other than INTA
> will likely cause problem when the number of assigned devices exceeds 8,
> e.g. dev 3, INTB and dev 11, INTA share the same girq. In this case, one
> machine may be left untracked and masked, any devices using the same
> machine irq (including those owned by other domains) is then blocked.
> 
> Just wonder if there is any need to expose multifunction devices (i.e.
> have to use INTB, etc.) to the guest in the future.
> 
> All comments and suggestions are welcomed.

Could you set the INT line to the function number? FN0->INTA, FN1->INTB,
...? This would then work for multi-fn devices, yet still most devices have
only fn0 and hence would use INTA as you desire.

 -- Keir



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


 


Rackspace

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