Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756567Ab0LQVNY (ORCPT ); Fri, 17 Dec 2010 16:13:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40024 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756507Ab0LQVNU (ORCPT ); Fri, 17 Dec 2010 16:13:20 -0500 Date: Fri, 17 Dec 2010 16:13:01 -0500 From: Vivek Goyal To: "H. Peter Anvin" Cc: Yinghai Lu , Stanislaw Gruszka , Ingo Molnar , Thomas Gleixner , Maxim Uvarov , "linux-kernel@vger.kernel.org" , Neil Horman Subject: Re: kdump broken on 2.6.37-rc4 Message-ID: <20101217211301.GK14502@redhat.com> References: <20101217170146.GC9568@redhat.com> <4D0BA45A.7020402@zytor.com> <20101217180242.GB12425@redhat.com> <4D0BAA24.3080801@kernel.org> <4D0BBC55.4010207@zytor.com> <4D0BBE00.3010602@kernel.org> <20101217195035.GE14502@redhat.com> <4D0BC067.90507@zytor.com> <20101217201104.GG14502@redhat.com> <4D0BCF32.8060400@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D0BCF32.8060400@zytor.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1244 Lines: 29 On Fri, Dec 17, 2010 at 12:59:30PM -0800, H. Peter Anvin wrote: > On 12/17/2010 12:11 PM, Vivek Goyal wrote: > >> > >> Can we do this in the meantime, just so we fix the immediate problem? > > > > Peter, kexec-tools on 64bit currently seems to be allowing loding bzImage > > till 896MB. So I am not too keen it to reduce it to 768MB in kernel just > > because x86_64 could be booted from even higher addresses and somebody > > first has to do some auditing and experiments. > > > > IMHO, we should have 768MB limit for 32bit and continue with 896MB limit for > > 64bit and once somebody makes x86_64 boot from even higher address reliably > > then we can change both kernel and kexec-tools. > > > > If we're splitting by architectures anyway, why not leave 32 bits at 512 > MiB and thus making older crashkernels usable just in case someone has a > frozen toolset? If you are more comfortable with 512MB for i386, that's fine with me. I care more for 64bit at this point of time. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/