Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754537Ab3CKTif (ORCPT ); Mon, 11 Mar 2013 15:38:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44966 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754466Ab3CKTid (ORCPT ); Mon, 11 Mar 2013 15:38:33 -0400 Date: Mon, 11 Mar 2013 15:38:24 -0400 From: Vivek Goyal To: Yinghai Lu Cc: "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , WANG Chao , "Eric W. Biederman" , linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86, kdump: Set crashkernel_low automatically Message-ID: <20130311193824.GA14738@redhat.com> References: <1362977817-23297-1-git-send-email-yinghai@kernel.org> <20130311144853.GB8482@redhat.com> <20130311150256.GC8482@redhat.com> <20130311182655.GB12107@redhat.com> <513E2695.3080707@zytor.com> <513E28B8.3000502@zytor.com> <20130311191031.GD12107@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: 951 Lines: 26 On Mon, Mar 11, 2013 at 12:34:00PM -0700, Yinghai Lu wrote: > On Mon, Mar 11, 2013 at 12:10 PM, Vivek Goyal wrote: > > Not breaking existing cases makes sense to me. > > that is -v2 version: > try 896M, then try 4G, than MAXMEM. > > > May be we should use > > a new parameter crashkernel_high to force memory reservation above > > 4G and crashkernel=X continues to reserve memory at lower addresses > > and remains backward compatible. > > No need to use crashkernel_high, we can just cashkernel=X@Y instead. crashkernel=X@Y is little different. It assumes user knows the memory map and location "Y" is fixed. There might not be any memory at "Y". So it is not same. 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/