From: David Vrabel <david.vrabel@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: avoid another early crash of memory limited dom0
Date: Fri, 28 Aug 2015 11:43:50 +0100 [thread overview]
Message-ID: <55E03B66.3040109@citrix.com> (raw)
In-Reply-To: <1440003191-4648-1-git-send-email-jgross@suse.com>
On 19/08/15 17:53, Juergen Gross wrote:
> Commit b1c9f169047b ("xen: split counting of extra memory pages...")
> introduced an error when dom0 was started with limited memory occurring
> only on some hardware.
>
> The problem arises in case dom0 is started with initial memory and
> maximum memory being the same. The kernel must be configured without
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen. If all
> of this is true and the E820 map of the machine is sparse (some areas
> are not covered) then the machine might crash early in the boot
> process.
Applied to for-linus-4.3, thanks.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@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: avoid another early crash of memory limited dom0
Date: Fri, 28 Aug 2015 11:43:50 +0100 [thread overview]
Message-ID: <55E03B66.3040109@citrix.com> (raw)
In-Reply-To: <1440003191-4648-1-git-send-email-jgross@suse.com>
On 19/08/15 17:53, Juergen Gross wrote:
> Commit b1c9f169047b ("xen: split counting of extra memory pages...")
> introduced an error when dom0 was started with limited memory occurring
> only on some hardware.
>
> The problem arises in case dom0 is started with initial memory and
> maximum memory being the same. The kernel must be configured without
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen. If all
> of this is true and the E820 map of the machine is sparse (some areas
> are not covered) then the machine might crash early in the boot
> process.
Applied to for-linus-4.3, thanks.
David
next prev parent reply other threads:[~2015-08-28 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 16:53 [PATCH] xen: avoid another early crash of memory limited dom0 Juergen Gross
2015-08-28 10:43 ` David Vrabel [this message]
2015-08-28 10:43 ` [Xen-devel] " 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=55E03B66.3040109@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.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.