RE: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11052

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

Alex,

Due to Cset11052 remove PIN processor for domaim0 vcpu0.
That means, VTI-domain and domain may share one LP,
But, VTI-domain uses do_block to emulate halt_ligh, while domain0 uses do_yield.
This makes VTI-domain scheduled less than domain0, 
and makes VTI-domain very slow, sometime crach due to time out.

After applying SAKAI's pal_halt_light patch, every thing seems Ok again.
If possible, please check in this patch ASAP.

BTW thanks SAKAI for your effort.


Thanks
Anthony




>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of You,
>Yongkang
>Sent: 2006年8月23日 14:22
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11052
>
>Xen/IA64 Healthiness Report
>A lot of testing cases failed in 11052, including VTI and XenU testing.
>
>Testing Environment:
>----------------------------
>Platform: Tiger4
>Processor: Itanium 2 Processor
>Logic Processors number: 8 (2 processors with Due Core)
>PAL version: 8.15
>Service OS: RHEL4u3 IA64
>VTI Guest OS: RHEL4u2 & RHEL4u3
>XenU Guest OS: RHEL4u2
>Xen IA64 Unstable tree: 11052:91169603a8e8
>Xen Schedule: bvt
>VTI Guest Firmware MD5: b6277539d86d785d8859ea2f99cf6013
>
>Summary Test Report:
>-----------------------------
>  Total cases: 15
>  Passed:    7
>  Failed:     8
>
>Detailed test cases info:
>-----------------------------
>One_VTI_without_vif                __fail__
>One_VTI                           __fail__
>One_XenU                         pass
>Two_VTI_Coexist                   pass
>One_VTI_and_One_XenU           __fail__
>Two_XenU_Coexist                 __fail__
>One_VTI_4096M                   pass
>VTI_Network                       pass
>XenU_Network                     pass
>One_SMP_XenU                   pass
>One_SMP_VTI                     __fail__
>UP_VTI_LTP                       pass
>VTI_Kernel_Build                   __fail__
>Four_VTI_Coexist                  __fail__
>VTI_Windows                      __fail__
>
>Notes:
>-----------------------------
>For VTI domain failures, there are several different phenomena.
>1. VTI domain kernel panic, when VTI domain booting.
>2. VTI domain hang just after uncompress VTI Linux kernel.
>3. VTI Qemu Window disappear.
>4. We also saw "oops: time before its due in VTI domain".
>
>The last stable changeset:
>-----------------------------
>10706:2db50529223e
>
>Best Regards,
>Yongkang (Kangkang) 永康
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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