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

["Han, Weidong" <weidong.han@xxxxxxxxx>]

Keir,

I found changeset 16331 breaks VT-d. When create guest with VT-d, qemu
window is white, and we see following messages on serial console:

(XEN) intel-iommu.c:1374:d0 reassign_device-1:0:0- source = 0 target = 1
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2214196 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2510520 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2515634 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2510520 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2515634 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2525556 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2513768 messages suppressed.
(XEN) mm.c:684:d2 Attempt to change cache attributes of Xen heap page
(XEN) printk: 2510754 messages suppressed.

Keir Fraser wrote:
> 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