All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] xen/arm64: do not (incorrectly) limit size of xenheap
Date: Fri, 4 Sep 2015 15:40:26 +0100	[thread overview]
Message-ID: <1441377626.26292.522.camel@citrix.com> (raw)
In-Reply-To: <20150904131627.GD27133@zion.uk.xensource.com>

On Fri, 2015-09-04 at 14:16 +0100, Wei Liu wrote:
> On Fri, Sep 04, 2015 at 01:57:00PM +0100, Julien Grall wrote:
> > The commit 88e3ed61642bb393458acc7a9bd2f96edc337190 "x86/NUMA: make
> > init_node_heap() respect Xen heap limit" breaks boot on the arm64 board
> > X-Gene.
> > 
> > The xenheap bits variable is used to know the last RAM MFN always 
> > mapped
> > in Xen virtual memory. If the value is 0, it means that all the memory 
> > is
> > always mapped in Xen virtual memory.
> > 
> > On X-gene the RAM bank resides above 128GB and last xenheap MFN is
> > 0x4400000. With the new way to calculate the number of bits, 
> > xenheap_bits
> > will be equal to 38 bits. This will result to hide all the RAM and the
> > impossibility to allocate xenheap memory.
> > 
> > Given that aarch64 have always all the memory mapped in Xen virtual
> > memory, it's not necessary to call xenheap_max_mfn which set the number
> > of bits.
> > 
> > Suggested-by: Jan Beulich <jbeulich@suse.com>
> > Signed-off-by: Julien Grall <julien.grall@citrix.com>
> > Acked-by: Ian Campbell <ian.campbell@citrix.com>
> > 
> 
> Release-acked-by: Wei Liu <wei.liu2@citrix.com>

Applied.

      reply	other threads:[~2015-09-04 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 12:57 [PATCH] xen/arm64: do not (incorrectly) limit size of xenheap Julien Grall
2015-09-04 13:16 ` Wei Liu
2015-09-04 14:40   ` Ian Campbell [this message]

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=1441377626.26292.522.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=wei.liu2@citrix.com \
    --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.