Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753216Ab3CKOtJ (ORCPT ); Mon, 11 Mar 2013 10:49:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2481 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130Ab3CKOtH (ORCPT ); Mon, 11 Mar 2013 10:49:07 -0400 Date: Mon, 11 Mar 2013 10:48:53 -0400 From: Vivek Goyal To: Yinghai Lu Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , WANG Chao , "Eric W. Biederman" , linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86, kdump: Set crashkernel_low automatically Message-ID: <20130311144853.GB8482@redhat.com> References: <513D52BA.3070206@redhat.com> <1362977817-23297-1-git-send-email-yinghai@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1362977817-23297-1-git-send-email-yinghai@kernel.org> 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: 1593 Lines: 41 On Sun, Mar 10, 2013 at 09:56:57PM -0700, Yinghai Lu wrote: > Current code does not set low range for crashkernel if the user > does not specify that. > > That cause regressions on system that does not support intel_iommu > properly. > > Chao said that his system does work well on 3.8 without extra parameter. > even iommu does not work with kdump. > > Set crashkernel_low automatically if the user does not specify that. > > For system that does support IOMMU with kdump properly, user could > specify crashkernel_low=0 to save that 72M low ram. > Hi Yinghai, Had a question about crashkernel_auto_low. So this is the amount of memory rerved under 4G. I am not very clear about the semantics here. So by default memory wil always come from areas above 4G (when crashkernel=X specified) and if user needs reserveation in lower memory area, it needs to be sepcified explicitly using crashkernel_low? But will that not break the case of exising bzImage which are 32bit. They currently work if I specify crashkernel=256M. Now suddenly memory will come from higher addresses and 32bit bzImage can't be loaded there. Or I understood the syntax part wrong. P.S. Explanation in kernel-parameters.txt is really short. Can you please add some explanation in kdump.txt to clarify how crashkernel_low is supposed to be used. 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/