From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: xen_phys_start for 32b Date: Wed, 07 Jan 2009 08:54:20 +0000 Message-ID: References: <4F65016F6CB04E49BFFA15D4F7B798D92D3E8263@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: <4F65016F6CB04E49BFFA15D4F7B798D92D3E8263@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 22:19, "Cihula, Joseph" wrote: >> It's not used for domheap either. In fact it's not really used at all. Hence >> encompassing it within xenheap_phys_start to xenheap_phys_end works okay. >> > > But shouldn't [xenheap_phys_start, xenheap_phys_end] represent all of the > memory that the hypervisor "owns" and which must be protected from even > privileged domain writes (modulo the real mode/trampoline code, which has its > own variables that represent its range)? While it may be "OK" on 32b systems, > it is not "logically correct" and does not match 64b systems (where this low > memory is not so protected). Would it break anything to set > xenheap_phys_start to __pa(&_start) for 32b builds? So what issue does this fix for you? -- Keir