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

Re: [Xen-devel] [VTD][PATCH] Support intra-domain shared interrupt


  • To: "Han, Weidong" <weidong.han@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Wed, 07 Nov 2007 15:09:14 +0000
  • Cc: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
  • Delivery-date: Wed, 07 Nov 2007 07:10:02 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgfbbYOsSWYB6MMQDuBGkYt+XjCJwAEwx4KAAASPxAAAXKGpgAAClDAAAJfMewAbWqM0AACgKoi
  • Thread-topic: [Xen-devel] [VTD][PATCH] Support intra-domain shared interrupt

Yes, I'll slip this one in.

 K.

On 7/11/07 15:02, "Han, Weidong" <weidong.han@xxxxxxxxx> wrote:

> Keir, how about this intra-domain shared interrupt patch? Attached patch
> fixes memory leak issue and updates timeout function. Thanks.
> 
> -- Weidong 
> 
> Keir Fraser wrote:
>> On 5/11/07 08:52, "Han, Weidong" <weidong.han@xxxxxxxxx> wrote:
>> 
>>> that situation two devices with different pyhsical IRQs getting
>>> aliased to the same guest GSI is hard to occur. And we need one
>>> guest GSI mapped to only one physical IRQ, or we can't know which
>>> device issues the guest GSI. Ideally, if we can make 1:1 mapping
>>> between guest GSI and physcial IRQ, the intra-domain shared
>>> interrupt can naturally handled by guest.
>> 
>> Ah, that's true. I suppose you can assign virtual devfn locations for
>> devices to purposely avoid aliasing in GSI space. What do you do about
>> aliasing into the ISA IRQ space?
>> 
>>  -- 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®.