[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130412200726.GC2253@redhat.com>
Date: Fri, 12 Apr 2013 16:07:27 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
WANG Chao <chaowang@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>
Subject: Re: [PATCH -v5 0/4] x86, kdump: Fix crashkernel high with old
kexec-tools
Hi hpa,
Can you please consider including these patches for 3.9. Today, another
kdump user ran into issues when he tried to use latest kernel (3.9-rcx)
with existing kexec-tools. Obiviously kernel loading failed due to
crashkernel memory being reserved too high.
Thanks
Vivek
On Thu, Apr 11, 2013 at 11:54:47PM -0700, Yinghai Lu wrote:
> Vivek found some problems with old kexec-tools.
>
> We keep the old crashkernel=X to old behavoir, so it will not break
> old kexec-tools.
> Add crashkernel=X,high to support new kexec-tools that supports loading high.
> when high is used, memblock will search from top to low.
> if the allocated one is above 4G, kernel will try to auto allocate
> 72M under 4G for swiotlb.
> user could crashkernel=Y,low to change 72M to other value.
>
> -v2: reorder the patch sequences
> crashkernel=X,high, crashkernel=Y,low only handle simple form.
> crashkernel=X will override crashkernel=X;high crashkernel=Y;low
> -v3: update description in kernel-parameters.txt
> update get_last_crashkernel and _simple checking about suffix.
> -v4: update to use ,high again, and also not abuse parse_crashkernel_simple
> -v5: tight checking about crashkernel=X,highextra,high
>
> Thanks
>
> Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists