From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752145AbbH1Kn6 (ORCPT ); Fri, 28 Aug 2015 06:43:58 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:46475 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751477AbbH1Knz (ORCPT ); Fri, 28 Aug 2015 06:43:55 -0400 X-IronPort-AV: E=Sophos;i="5.17,424,1437436800"; d="scan'208";a="298897575" Message-ID: <55E03B66.3040109@citrix.com> Date: Fri, 28 Aug 2015 11:43:50 +0100 From: David Vrabel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Juergen Gross , , , , , Subject: Re: [Xen-devel] [PATCH] xen: avoid another early crash of memory limited dom0 References: <1440003191-4648-1-git-send-email-jgross@suse.com> In-Reply-To: <1440003191-4648-1-git-send-email-jgross@suse.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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