From: Julien Grall <julien.grall@linaro.org>
To: Thomas Leonard <talex5@gmail.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
tim@xen.org
Subject: Re: [PATCH] libxc: arm: Load the zImage to the rambase address + 2MB
Date: Thu, 03 Jul 2014 12:12:18 +0100 [thread overview]
Message-ID: <53B53A92.4090003@linaro.org> (raw)
In-Reply-To: <53B53262.8050703@gmail.com>
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
next prev parent reply other threads:[~2014-07-03 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:05 [PATCH] libxc: arm: Load the zImage to the rambase address + 2MB Julien Grall
2014-07-03 10:01 ` Ian Campbell
2014-07-03 10:12 ` Julien Grall
2014-07-03 10:37 ` Thomas Leonard
2014-07-03 11:12 ` Julien Grall [this message]
2014-07-03 11:19 ` Ian Campbell
2014-07-03 10:39 ` Thomas Leonard
2014-07-03 11:18 ` Ian Campbell
2014-07-03 12:21 ` Julien Grall
2014-07-03 13:54 ` Ian Campbell
2014-07-03 11:17 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B53A92.4090003@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=talex5@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.