linux-kernel - Re: [PATCH] x86, kdump: Set crashkernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQVP2NYV_6XvWEoLHYz8R_Zvueq6zqhh1cKq85geRwWzyA@mail.gmail.com>
Date:	Mon, 11 Mar 2013 12:44:15 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Vivek Goyal <vgoyal@...hat.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>,
	WANG Chao <chaowang@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86, kdump: Set crashkernel_low automatically

On Mon, Mar 11, 2013 at 12:39 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Mon, Mar 11, 2013 at 12:38 PM, Vivek Goyal <vgoyal@...hat.com> wrote:
>>> No need to use crashkernel_high, we can just cashkernel=X@Y instead.
>>
>> crashkernel=X@Y is little different. It assumes user knows the memory
>> map and location "Y" is fixed. There might not be any memory at "Y".
>
> then use crashkernel=4G?

I re attached -v2 and -v3.

I'm ok that any one is applied or two get applied all together.

only affect 64bit
-v2: try under under 896M, then 4G, then MAXMEM
-v3: auto set crashkernel_low with swiotlb size.

Thanks

Yinghai

Download attachment "fix_crashkernel_low_v2.patch" of type "application/octet-stream" (3329 bytes)

Download attachment "fix_crashkernel_low_v3.patch" of type "application/octet-stream" (3737 bytes)