All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>, WANG Chao <chaowang@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] x86, kdump: Retore crashkernel= to allocate low
Date: Thu, 4 Apr 2013 10:16:04 -0400	[thread overview]
Message-ID: <20130404141604.GD16459@redhat.com> (raw)
In-Reply-To: <1365035906-3208-4-git-send-email-yinghai@kernel.org>

On Wed, Apr 03, 2013 at 05:38:25PM -0700, Yinghai Lu wrote:
> Vivek found old kexec-tools does not work new kernel anymore.
> 
> So change back crashkernel= back to old behavoir, and add crashkernel_high=
> to let user decide if buffer could be above 4G, and also new kexec-tools will
> be needed.
> 
> v2: let crashkernel=X override crashkernel_high=
>     update description about _high will be ignored by crashkernel=X
> 
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> 
> ---
>  Documentation/kernel-parameters.txt |   11 +++++++++--
>  arch/x86/kernel/setup.c             |   24 +++++++++++++++++++-----
>  include/linux/kexec.h               |    2 ++
>  kernel/kexec.c                      |    9 +++++++++
>  4 files changed, 39 insertions(+), 7 deletions(-)
> 
> Index: linux-2.6/Documentation/kernel-parameters.txt
> ===================================================================
> --- linux-2.6.orig/Documentation/kernel-parameters.txt
> +++ linux-2.6/Documentation/kernel-parameters.txt
> @@ -603,9 +603,14 @@ bytes respectively. Such letter suffixes
>  			a memory unit (amount[KMG]). See also
>  			Documentation/kdump/kdump.txt for an example.
>  
> +	crashkernel_high=size[KMG]
> +			[KNL, x86_64] range could be above 4G. Allow kernel
> +			to allocate physical memory region from top, so could
> +			be above 4G if system have more than 4G ram installed.

Also specify "otherwise memory will be allocated below 4G, if available".

> +			It will be ignored if crashkernel=X is specified.
>  	crashkernel_low=size[KMG]
> -			[KNL, x86_64] range under 4G. When crashkernel= is
> -			passed, kernel allocate physical memory region
> +			[KNL, x86_64] range under 4G. When crashkernel_high= is
> +			passed, kernel could allocate physical memory region
>  			above 4G, that cause second kernel crash on system
>  			that need swiotlb later. Kernel would try to allocate
>  			some region below 4G automatically. This one let
> @@ -614,6 +619,8 @@ bytes respectively. Such letter suffixes
>  			0: to disable low allocation on systems that do not
>  			need swiotlb, that will save 72M low ram in first
>  			kernel.
> +			It will be ignored when crashkernel_high=X is not used
> +			or return from that is below 4G.

Replace "return from that" with "memory reserved".

Vivek

  reply	other threads:[~2013-04-04 14:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  0:38 [PATCH -v2 0/4] x86, kdump: Fix crashkernel high with old kexec-tools Yinghai Lu
2013-04-04  0:38 ` [PATCH v2 1/4] x86, kdump: Set crashkernel_low automatically Yinghai Lu
2013-04-04  8:11   ` HATAYAMA Daisuke
2013-04-04 16:45     ` Yinghai Lu
2013-04-04 14:11   ` Vivek Goyal
2013-04-04 16:28     ` Yinghai Lu
2013-04-04  0:38 ` [PATCH v2 3/4] kexec: use Crash kernel for Crash kernel low Yinghai Lu
2013-04-04  0:38 ` [PATCH v2 2/4] x86, kdump: Retore crashkernel= to allocate low Yinghai Lu
2013-04-04 14:16   ` Vivek Goyal [this message]
2013-04-04 16:56     ` Yinghai Lu
2013-04-04  0:38 ` [PATCH v2 4/4] x86, kdump: Change crashkernel_high/low= to crashkernel=;high/low Yinghai Lu
2013-04-04  6:55   ` HATAYAMA Daisuke
2013-04-04 17:33     ` Yinghai Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130404141604.GD16459@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=chaowang@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.