All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
	Maxim Uvarov <maxim.uvarov@oracle.com>
Subject: Re: [Xen-devel] Re: [PATCH] XEN_DOMAIN_MEMORY options.
Date: Wed, 19 Oct 2011 10:05:25 -0400	[thread overview]
Message-ID: <20111019140525.GC7313@phenom.dumpdata.com> (raw)
In-Reply-To: <1318696968.11016.47.camel@dagon.hellion.org.uk>

On Sat, Oct 15, 2011 at 05:42:48PM +0100, Ian Campbell wrote:
> On Sat, 2011-10-15 at 09:05 -0400, Konrad Rzeszutek Wilk wrote:
> > > On 10/14/2011 04:41 PM, Jeremy Fitzhardinge wrote:
> 
> > > >While it would be very silly to put 128GB of actual RAM on a 32-bit
> > > >machine, systems can have non-contiguous RAM placed at high addresses,
> > > >which would no longer be accessible.
> > 
> > Do you have some ideas of which machines that might be?
> 
> Even if you were on such a machine, the discontiguity
> (discontiguousness?) wouldn't ever be reflected in the pseudo-physical
> memory map, would it? So since this variable controls the maximum size
> of the p2m (rather than the m2p) it doesn't need to be larger than the
> maximum sane 32 bit guest size (<64G).

I think it is the other way around. The M2P would not be affected but
the P2M might? The "discontinuity" is in the E820 right? (so mega big
holes in it).

  reply	other threads:[~2011-10-19 14:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 22:36 [PATCH] XEN_DOMAIN_MEMORY options Maxim Uvarov
2011-10-14 22:36 ` [PATCH 1/2] xen: Fix XEN_MAX_DOMAIN_MEMORY to be selectable Maxim Uvarov
2011-10-14 22:36 ` [PATCH 2/2] xen: Make XEN_MAX_DOMAIN_MEMORY have more sensible defaults for 32-bit builds Maxim Uvarov
2011-10-14 23:00 ` [PATCH] XEN_DOMAIN_MEMORY options Jeremy Fitzhardinge
2011-10-14 23:33   ` Maxim Uvarov
2011-10-14 23:41     ` Jeremy Fitzhardinge
2011-10-15  0:43       ` Maxim Uvarov
2011-10-15 13:05         ` Konrad Rzeszutek Wilk
2011-10-15 16:42           ` Ian Campbell
2011-10-19 14:05             ` Konrad Rzeszutek Wilk [this message]
2011-10-19 14:04           ` Konrad Rzeszutek Wilk
2011-10-19 14:04             ` Konrad Rzeszutek Wilk

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=20111019140525.GC7313@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ijc@hellion.org.uk \
    --cc=jeremy@goop.org \
    --cc=konrad@darnok.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxim.uvarov@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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.