RE: [Xen-ia64-devel] [PATCH 1/2] [RESEND] FPSWA emulation support

Hi Dan/Alex, Thanks for your information and advice. I will correct and resend this patch. - I remove handle_fpu_swa_for_xen(). and, - When an FP error occurs in Xen, Xen does the panic. Best regards, Kan Why do we need handle_fpu_swa_for_xen()? Xen should never hit an FP error that

RE: VTI hitting the blocked state (wasRE:[PATCH][RESEND]RE:[Xen-ia64-devel] [PATCH 0/6] Addfullevtchnmechanism forxen/ia64)

As a step to reduce suspicious points, I tried similar experiment on Rev 10138 ([IA64] update default build configs) before the evtchn patch sets and then I observed same 'block' issue for VTI domain. Investigation is on going. Thanks, Kevin -Original Message- From: Tian, Kevin Sent:

[Xen-ia64-devel] [PATCH 1/2] [RESEND*2] FPSWA emulation support

1/2 FPSWA-emulation.patch Description: Binary data ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel

RE: [Xen-ia64-devel] [PATCH] [RESEND][PATCH 1/3]clean up vti code

Hi Alex, Please ignore this patch. Thanks, -Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xu, Anthony Sent: 2006?5?25? 22:27 To: Alex Williamson; Zhang, Xiantao Cc: xen-ia64-devel@lists.xensource.com Subject: RE: [Xen-ia64-devel] [PATCH]

Re: [Xen-ia64-devel] [PATCH 0/2] [RESEND*2] FPSWA emulation support

On Thu, 2006-05-25 at 21:53 +0900, Masaki Kanno wrote: Hi, These patches have reflected all comments. I tested these patches by LTP. Xen passed about floating point tests. Applied. -- Alex Williamson HP Linux Open Source Lab

RE: [Xen-ia64-devel] kernel build performance data with dom0_VPmodeopen

I'm surprised too, It is 256x smaller VHPT size. We need to get performance data with P=M and VHPT=64k. Thanks, -Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Magenheimer, Dan (HP Labs Fort Collins) Sent: 2006?5?26? 1:29 To: Isaku Yamahata Cc:

Re: [Xen-ia64-devel] kernel build performance data with dom0_VPmodeopen

64MB was wrong. 16MB VHPT for P=M. On Fri, May 26, 2006 at 09:31:16AM +0800, Xu, Anthony wrote: I'm surprised too, It is 256x smaller VHPT size. We need to get performance data with P=M and VHPT=64k. Thanks, -Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL

Re: [Xen-ia64-devel] kernel build performance data with dom0_VP modeopen

On Thu, May 25, 2006 at 10:28:30AM -0700, Magenheimer, Dan (HP Labs Fort Collins) wrote: For dom0vp model, VHPT size is reduced to 64KBytes to avoid triggering software lock detection. For P=M model, its size remain 64MB. It would be interesting to measure on P=M model with 64KBtyes