From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: [PATCH] Re: dom0 boot failure with 256G Date: Thu, 05 Jun 2008 19:43:38 -0700 Message-ID: <4848A45A.1060504@oracle.com> References: <48474A61.3050903@oracle.com> <4847B36A.76E4.0078.0@novell.com> Reply-To: mukesh.rathor@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4847B36A.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: "Kurt C. Hackel" , Keir Fraser , xen-devel List-Id: xen-devel@lists.xenproject.org Jan Beulich wrote: >> Trying to figure the hyp out, I notice phys addr is set as: >> >> d->arch.physaddr_bitsize = >> fls((1UL << 32) - HYPERVISOR_COMPAT_VIRT_START(d)) - 1 >> + (PAGE_SIZE - 2); >> which is set to 0x1019, totally baffling me. I'd expect it to be 32, >> 36, or 64???????? > > Of course it should be PAGE_SHIFT in here! c/s 14097 screwed this up > - sorry, my fault. > Yup, that fixed it. Can you pl explain in couple sentences how we are getting at the physaddr_bitsize here? I still don't understand why 37 is an OK size for a 32-PAE guest (i thought 36 was max). Thanks, Mukesh