29 messages in com.xensource.lists.xen-ia64-develRE: [Xen-ia64-devel][Patch]Add two PA...
FromSent OnAttachments
Zhang, Xing Z26 Mar 2007 18:17.patch
Masaki Kanno26 Mar 2007 18:50 
Zhang, Xing Z26 Mar 2007 18:53 
Kouya SHIMURA26 Mar 2007 19:14.patch
Zhang, Xing Z26 Mar 2007 19:47 
Alex Williamson27 Mar 2007 09:42 
Zhang, Xing Z27 Mar 2007 19:00 
Alex Williamson27 Mar 2007 19:26 
Zhang, Xing Z27 Mar 2007 19:45 
Alex Williamson27 Mar 2007 21:39 
Xu, Anthony28 Mar 2007 00:00 
Alex Williamson03 Apr 2007 11:53 
Kouya SHIMURA04 Apr 2007 05:25.patch
Alex Williamson04 Apr 2007 11:22 
tgin...@free.fr04 Apr 2007 12:00 
Zhang, Xing Z04 Apr 2007 20:32 
Kouya SHIMURA04 Apr 2007 21:33 
Tristan Gingold04 Apr 2007 21:56 
Kouya SHIMURA04 Apr 2007 22:51 
Zhang, Xing Z04 Apr 2007 23:05 
tgin...@free.fr05 Apr 2007 00:40 
Kouya SHIMURA05 Apr 2007 00:54 
Zhang, Xing Z05 Apr 2007 00:59 
Zhang, Xing Z05 Apr 2007 01:03 
Zhang, Xing Z05 Apr 2007 04:30 
Xu, Anthony05 Apr 2007 08:41 
Zhang, Xing Z09 Apr 2007 02:12 
Alex Williamson09 Apr 2007 09:46 
Zhang, Xing Z10 Apr 2007 18:56 
Subject:RE: [Xen-ia64-devel][Patch]Add two PAL calls which fix SMP windowsinstallation crashing bug
From:Zhang, Xing Z (xing@intel.com)
Date:03/27/2007 07:00:01 PM
List:com.xensource.lists.xen-ia64-devel

Hi Alex: Pls see my comments.

This seems incomplete. Doesn't a PAL_LOGICAL_TO_PHYSICAL implementation imply we also need a working SAL_PHYSICAL_ID_INFO? I also get error messages about unimplemented PAL call #43 (PAL_CACHE_SHARED_INFO) when I try this. According to the spec, this call is required for any system reporting more than one logical processor on a physical processor package.

Yes, we need implement these PAL calls and SAL calls. Due to the two PAL calls -- PAL_LOGICAL_TO_PHSICAL and PAL_FIX_ADDR emergently fix SMP windows
installation crashing bug, so I sent out it firstly. Other PALL calls patch
which in need will be sent out later.

I think we should implement these calls, but why would we represent a vCPU as anything more than a single processor per socket? If we pretend everything is a dual core processor with threads disabled, we get into issues of reporting the correct socket number and thread number. It feels like it's just adding complication for no benefit. Thanks,

Actually, we also represent a vcpu as single core single thread at beginning.
But it's very strange that windows still crash during SMP installation. So we
implement it as native Montecito which has dual core. Maybe more investigations
need.

Good good study,day day up ! ^_^ -Wing(zhang xin)

OTC,Intel Corporation

-----Original Message----- From: Alex Williamson [mailto:alex@hp.com] Sent: 2007年3月28日 0:43 To: Zhang, Xing Z Cc: xen-ia64-devel Subject: Re: [Xen-ia64-devel][Patch]Add two PAL calls which fix SMP windowsinstallation crashing bug

On Tue, 2007-03-27 at 09:18 +0800, Zhang, Xing Z wrote:

Add two PAL calls -- PAL_LOGICAL_TO_PHYSICAL and PAL_FIXED_ADDR.

These PAL calls are invoked by SMP windows installation code.

The patch fix SMP windows installation crashing bug.

This seems incomplete. Doesn't a PAL_LOGICAL_TO_PHYSICAL implementation imply we also need a working SAL_PHYSICAL_ID_INFO? I also get error messages about unimplemented PAL call #43 (PAL_CACHE_SHARED_INFO) when I try this. According to the spec, this call is required for any system reporting more than one logical processor on a physical processor package.

I think we should implement these calls, but why would we represent a vCPU as anything more than a single processor per socket? If we pretend everything is a dual core processor with threads disabled, we get into issues of reporting the correct socket number and thread number. It feels like it's just adding complication for no benefit. Thanks,

Alex

-- Alex Williamson HP Open Source & Linux Org.

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