From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] [PATCH] arch/x86/xen/setup: Fix for incorrect xen_extra_mem_start initialization ifdef CONFIG_X86_32 Date: Thu, 12 May 2011 14:58:08 -0400 Message-ID: <20110512185808.GA26281@dumpdata.com> References: <20110511203438.GA21034@router-fw-old.local.net-space.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110511203438.GA21034@router-fw-old.local.net-space.pl> Sender: linux-kernel-owner@vger.kernel.org To: Daniel Kiper Cc: stefano.stabellini@eu.citrix.com, linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, May 11, 2011 at 10:34:38PM +0200, Daniel Kiper wrote: > git commit 24bdb0b62cc82120924762ae6bc85afc8c3f2b26 (xen: do not create > the extra e820 region at an addr lower than 4G) does not take into > account that ifdef CONFIG_X86_32 instead of e820_end_of_low_ram_pfn() > find_low_pfn_range() is called (both calls are from arch/x86/kernel/setup.c). > find_low_pfn_range() behaves correctly and does not require change in > xen_extra_mem_start initialization. Additionally, if xen_extra_mem_start > is initialized in the same way as ifdef CONFIG_X86_64 then memory hotplug > support for Xen balloon driver (under development) is broken. in linux-next.