From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 10/28] i386: map enough initial memory to create lowmem mappings Date: Thu, 19 Apr 2007 14:11:40 -0700 Message-ID: <4627DB0C.2010804@zytor.com> References: <20070414204154.871250608@goop.org> <200704192250.52633.ak@suse.de> <4627D756.5020405@zytor.com> <200704192304.01053.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200704192304.01053.ak@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Andi Kleen Cc: lkml , Chris Wright , virtualization@lists.osdl.org, "Eric W. Biederman" , Chuck Ebbert , Andrew Morton , Linus Torvalds List-Id: virtualization@lists.linuxfoundation.org Andi Kleen wrote: > On Thursday 19 April 2007 22:55:50 H. Peter Anvin wrote: >> Andi Kleen wrote: >>>> Is some version of this going in for 2.6.21, or is it not a real problem? >>> When it's only seen with Xen it's not a real problem right now. >> It's not just seen only with Xen, though. It will affect all kernels in >> a particular range of sizes, and we have ordinary kernels covering that >> range (in fact, Xen hardly affects size in that way.) > > Then we would have seen reports surely? The critical size window is relatively small, though. The size of the uncompressed kernel mod 4 MB must be above 3.75 MB or so. If you have less than 1 GB RAM, the window is even smaller. This is strictly configuration-dependent, and has nothing to do with Xen. It just so happened that the first people to detect and diagnose it (as opposed to just "it doesn't boot") were Xen people. -hpa