All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
	<xen-devel@lists.xensource.com>, <konrad.wilk@oracle.com>,
	<david.vrabel@citrix.com>, <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH] xen: limit memory to architectural maximum
Date: Fri, 4 Sep 2015 16:08:09 +0200	[thread overview]
Message-ID: <55E9A5C9.1030201@citrix.com> (raw)
In-Reply-To: <1441369088-11680-1-git-send-email-jgross@suse.com>

El 04/09/15 a les 14.18, Juergen Gross ha escrit:
> When a pv-domain (including dom0) is started it tries to size it's
> p2m list according to the maximum possible memory amount it ever can
> achieve. Limit the initial maximum memory size to the architectural
> limit of the hardware in order to avoid overflows during remapping
> of memory.
> 
> This problem will occur when dom0 is started with an initial memory
> size being a multiple of 1GB, but without specifying it's maximum
> memory size. The kernel must be configured without
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen.
> 
> Reported-by: Roger Pau Monné <roger.pau@citrix.com>
> Signed-off-by: Juergen Gross <jgross@suse.com>

Tested-by: Roger Pau Monné <roger.pau@citrix.com>


WARNING: multiple messages have this Message-ID (diff)
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	konrad.wilk@oracle.com, david.vrabel@citrix.com,
	boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [PATCH] xen: limit memory to architectural maximum
Date: Fri, 4 Sep 2015 16:08:09 +0200	[thread overview]
Message-ID: <55E9A5C9.1030201@citrix.com> (raw)
In-Reply-To: <1441369088-11680-1-git-send-email-jgross@suse.com>

El 04/09/15 a les 14.18, Juergen Gross ha escrit:
> When a pv-domain (including dom0) is started it tries to size it's
> p2m list according to the maximum possible memory amount it ever can
> achieve. Limit the initial maximum memory size to the architectural
> limit of the hardware in order to avoid overflows during remapping
> of memory.
> 
> This problem will occur when dom0 is started with an initial memory
> size being a multiple of 1GB, but without specifying it's maximum
> memory size. The kernel must be configured without
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen.
> 
> Reported-by: Roger Pau Monné <roger.pau@citrix.com>
> Signed-off-by: Juergen Gross <jgross@suse.com>

Tested-by: Roger Pau Monné <roger.pau@citrix.com>

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 12:18 [PATCH] xen: limit memory to architectural maximum Juergen Gross
2015-09-04 14:08 ` Roger Pau Monné [this message]
2015-09-04 14:08   ` [Xen-devel] " Roger Pau Monné
2015-09-04 15:43 ` David Vrabel
2015-09-04 15:43   ` David Vrabel

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=55E9A5C9.1030201@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.