xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	tim@xen.org, Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH] xen/arm: Allocate memory for dom0 from the bottom with the 1:1 Workaround
Date: Tue, 22 Oct 2013 15:01:27 +0100	[thread overview]
Message-ID: <1382450487.18283.13.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <CAPnVf8wvMPUpORxFzzLhCor+k1S4fqGKLd4RwDbRac+Qp=nQtw@mail.gmail.com>

On Tue, 2013-10-22 at 14:58 +0100, Julien Grall wrote:
> On 22 October 2013 12:26, Ian Campbell <ian.campbell@citrix.com> wrote:
> > On Tue, 2013-10-22 at 11:51 +0100, Julien Grall wrote:
> >> On Linux, the option CONFIG_ARM_PATCH_PHYS_VIRT (by default enabled) allows
> >> the Kernel to be loaded anywhere (or nearly) by patching the translation
> >> pv<->virt at boot time.
> >>
> >> The current solution in Linux assuming that the delta physical address -
> >> virtual address is always negative. A positive delta will destroy all the
> >> optimisation to modify only a part of the translation instruction (add/sub).
> >>
> >> By default, Xen is allocating memory from the top of memory and then
> >> goes down. To avoid booting issue with Linux, we must allocate memory
> >> from the bottom (ie starting from 0).
> >>
> >> Signed-off-by: Julien Grall <julien.grall@linaro.org>
> >
> > Acked-by: Ian Campbell <ian.campbell@citrix.com>
> >
> > OOI how low does the memory get allocated in practice? We deliberately
> > load Xen and place xenheap up high so I guess for dom0 we can't get
> > memory from pretty low down?
> 
> It depends where U-boot has loaded the different modules (kernel,
> initrd, device tree,...).
> If they are not loaded at the bottom of the RAM, Xen is able to use
> the first address of the first bank.

Great! That's what I was hoping.

Thanks,
Ian.

  reply	other threads:[~2013-10-22 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 10:51 [PATCH] xen/arm: Allocate memory for dom0 from the bottom with the 1:1 Workaround Julien Grall
2013-10-22 11:26 ` Ian Campbell
2013-10-22 13:58   ` Julien Grall
2013-10-22 14:01     ` Ian Campbell [this message]
2013-10-24 14:05   ` 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=1382450487.18283.13.camel@hastur.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=patches@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).