From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1O5BGg-0004MP-9q for kexec@lists.infradead.org; Fri, 23 Apr 2010 05:17:34 +0000 Message-ID: <4BD12E48.3080400@redhat.com> Date: Fri, 23 Apr 2010 13:21:12 +0800 From: Cong Wang MIME-Version: 1.0 Subject: Re: [PATCH 0/5] Add second memory region for crash kernel References: <1271953392-6324-1-git-send-email-v.mayatskih@gmail.com> <20100422224525.GJ3228@redhat.com> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: "Eric W. Biederman" Cc: Vitaly Mayatskikh , Neil Horman , kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Haren Myneni , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , Vivek Goyal Eric W. Biederman wrote: > Vivek Goyal writes: > >> Vitaly, have you really run into cases where 2G upper limit is a concern. >> What is the configuration you have, how much memory it has and how much >> memory are you planning to reserve for kdump kernel? > > A good question. > We have observed that on a machine which has 66G memory, when we do crashkernel=1G@4G, kexec failed to load the crash kernel, but the memory reservation _did_ succeed. Thanks. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755708Ab0DWFRt (ORCPT ); Fri, 23 Apr 2010 01:17:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43215 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755616Ab0DWFRq (ORCPT ); Fri, 23 Apr 2010 01:17:46 -0400 Message-ID: <4BD12E48.3080400@redhat.com> Date: Fri, 23 Apr 2010 13:21:12 +0800 From: Cong Wang User-Agent: Thunderbird 2.0.0.23 (X11/20091001) MIME-Version: 1.0 To: "Eric W. Biederman" CC: Vivek Goyal , Vitaly Mayatskikh , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Haren Myneni , Neil Horman , kexec@lists.infradead.org Subject: Re: [PATCH 0/5] Add second memory region for crash kernel References: <1271953392-6324-1-git-send-email-v.mayatskih@gmail.com> <20100422224525.GJ3228@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Eric W. Biederman wrote: > Vivek Goyal writes: > >> Vitaly, have you really run into cases where 2G upper limit is a concern. >> What is the configuration you have, how much memory it has and how much >> memory are you planning to reserve for kdump kernel? > > A good question. > We have observed that on a machine which has 66G memory, when we do crashkernel=1G@4G, kexec failed to load the crash kernel, but the memory reservation _did_ succeed. Thanks.