From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: xen_phys_start for 32b Date: Tue, 06 Jan 2009 08:42:47 +0000 Message-ID: References: <4F65016F6CB04E49BFFA15D4F7B798D92D3E7CA9@orsmsx506.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F65016F6CB04E49BFFA15D4F7B798D92D3E7CA9@orsmsx506.amr.corp.intel.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: "Cihula, Joseph" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/01/2009 06:36, "Cihula, Joseph" wrote: > On 64b builds of Xen, xen_phys_start holds the starting (physical) address of > the hypervisor. However, on 32b systems it is 0. While I realize that 32b > Xen does not relocate the hypervisor, why not set this variable to the start > of the code (__pa(&_start)) so that it will represent the same thing on all > builds? For both i386 and x86/64: __pa(&_start) == xen_phys_start + 1ul<<20 xen_phys_start marks the start of the Xen heap, which Xen text and data is embedded within. -- Keir