Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754414Ab3J1Fs1 (ORCPT ); Mon, 28 Oct 2013 01:48:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:3429 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752112Ab3J1FsZ (ORCPT ); Mon, 28 Oct 2013 01:48:25 -0400 Date: Mon, 28 Oct 2013 13:47:39 +0800 From: Dave Young To: Yinghai Lu Cc: Vivek Goyal , WANG Chao , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Pekka Enberg , Jacob Shin , Andrew Morton , "Eric W. Biederman" , "kexec@lists.infradead.org" , Linux Kernel Mailing List Subject: Re: [PATCH] x86, kdump: crashkernel=X try to reserve below 896M first, then try below 4G, then MAXMEM Message-ID: <20131028054739.GA20741@dhcp-16-126.nay.redhat.com> References: <1381751200-27376-1-git-send-email-chaowang@redhat.com> <20131015144810.GI31215@redhat.com> <20131018123837.GB2277@redhat.com> <20131021151643.GA20669@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 783 Lines: 20 > Again, for distribution, when new kernel is added, new kernel will all > have ",high" > and new kexec-tools get installed. > > Even we want to extend crashkernel=XM, then i would like to have > it identical to crashkernel=XM,high instead. My points: I can accept the approach of extending crashkernel=XM to use high mem firstly if we could remove the extra 72M in low mem, but apparently it's not doable now. So I would vote for Chao's patch. Also newer kernel use more complex ",high" then older kernel looks not good. Thanks Dave -- 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/