RE: [Xen-ia64-devel] [PATCH] Add support to physdev_ops

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>Sent: 2006年4月21日 9:30
>
>
>
>diff -r 7ed4420aac6b -r e6bffdbbd0e2 xen/arch/ia64/xen/hypercall.c
>--- a/xen/arch/ia64/xen/hypercall.c     Thu Apr 20 02:05:24 2006
>+++ b/xen/arch/ia64/xen/hypercall.c     Thu Apr 20 03:08:42 2006
>
>-       (hypercall_t)do_ni_hypercall,           /* do_physdev_op */
>+       (hypercall_t)do_ni_hypercall,           /* do_physdev_op */
>                     ^^^^^^^^^^^^^^^
>                     do_physdev_op?
>

Thanks, I ignored that in the start because no one in hypercall.c 
uses that table. I'll add it.

Thanks
Kevin

>
>On Thu, Apr 20, 2006 at 05:01:31PM +0800, Tian, Kevin wrote:
>> Add support to physdev ops, and thus give IOSAPIC RTEs
>> managed by Xen now. Dom0 now issues hypercall to r/w
>> RTE entry. Another change is the irq vector allocation
>> which is also owned by xen now.
>>
>> After this change, the IOSAPIC is almost owned by xen
>> with only exception as IOSAPIC EOI which is still issued
>> by dom0 directly. But that's OK since currently dom0
>> owns all external physical devices. Later full event
>> channel mechanism will provide necessary support for
>> driver domain, and at that time, dom0 instead issues
>> physdev_op (PHYSDEVOP_IRQ_UNMASK_NOTIFY) naturally
>> as replace of IOSAPIC EOI.
>>
>> Signed-off-by Kevin Tian <kevin.tian@xxxxxxxxx>
>>
>> N.B.
>> 1. This patch needs to be applied after pulling necessary
>> files as requested in another thread.
>>
>> 2. This patch has no obvious performance influence (Why
>> I say 'obvious' is because latest p2m tree seems not very
>> stable even without this patch. The output drifts with -10-+10%
>> range... It's also possible due to my test environment. )
>>
>> Thanks,
>> Kevin
>
>
>> _______________________________________________
>> Xen-ia64-devel mailing list
>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel
>
>--
>yamahata

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