From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761311Ab3DDNvW (ORCPT ); Thu, 4 Apr 2013 09:51:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:18018 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760635Ab3DDNvV (ORCPT ); Thu, 4 Apr 2013 09:51:21 -0400 Date: Thu, 4 Apr 2013 09:51:08 -0400 From: Vivek Goyal To: Yinghai Lu Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , WANG Chao , "Eric W. Biederman" , Linux Kernel Mailing List Subject: Re: [PATCH 3/4] x86, kdump: Retore crashkernel= to allocate low Message-ID: <20130404135108.GB16459@redhat.com> References: <20130402201148.GJ29506@redhat.com> <20130403131842.GA5939@redhat.com> <20130403174734.GG5939@redhat.com> <20130403210019.GH5939@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 On Wed, Apr 03, 2013 at 05:56:00PM -0700, Yinghai Lu wrote: [..] > > One big rang under 4G is working well till second kernel need more than 512M > on bigger system with more memory. Currently one range is allocated below 896MB (and not 4G). So if we extend crashkernel=X to first try below 896MB and then reserve below 4G, we are just fine. And in fact we should be able to extend to even look beyond 4G if nothing suitable is available below 4G. Thanks Vivek