From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH] libxc: arm: Load the zImage to the rambase address + 2MB Date: Thu, 03 Jul 2014 12:12:18 +0100 Message-ID: <53B53A92.4090003@linaro.org> References: <1404137113-25101-1-git-send-email-julien.grall@linaro.org> <1404381702.14865.35.camel@kazak.uk.xensource.com> <53B52C82.500@linaro.org> <53B53262.8050703@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X2ewB-0006l5-IX for xen-devel@lists.xenproject.org; Thu, 03 Jul 2014 11:12:23 +0000 Received: by mail-wg0-f50.google.com with SMTP id m15so58547wgh.9 for ; Thu, 03 Jul 2014 04:12:21 -0700 (PDT) In-Reply-To: <53B53262.8050703@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Thomas Leonard , Ian Campbell Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com, tim@xen.org List-Id: xen-devel@lists.xenproject.org On 07/03/2014 11:37 AM, Thomas Leonard wrote: >> Using 4K alignment make impossible to use 1MB or 2MB mapping for early >> page table. Which make the code (usually in assembly) even harder to >> write or to impose relocation in the assembly code. > > This isn't the case for Mini-OS, at least. We already use a 1MB mapping > with the 0x8000 offset just fine. The translation table (using 1MB > sections) is 16K, which would fit nicely in the 0x8000 gap (although > currently we don't use that space). As I said in Mini-OS series, the spec doesn't say anything about the start offset of the guest kernel for the Linux boot protocol. 0x8000 offset is very inconvenient for most of the other OS than Linux. As Linux is able to relocate itself, I don't see any known issue about starting at an 2MB-aligned address. > Starting at 2MB would create an inconvenient 2MB of free memory just > before the kernel, with no obvious way to tell xmalloc about it. That's a bug in Mini-OS in this case. Why can't you use the whole memory? Regards, -- Julien Grall