| 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
| ||
|
Date: Tue, 2 Apr 2013 13:04:58 -0700 From: Yinghai Lu <yinghai@...nel.org> To: Vivek Goyal <vgoyal@...hat.com> Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>, WANG Chao <chaowang@...hat.com>, "Eric W. Biederman" <ebiederm@...ssion.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 3/4] x86, kdump: Retore crashkernel= to allocate low On Tue, Apr 2, 2013 at 12:09 PM, Vivek Goyal <vgoyal@...hat.com> wrote: >> >> Actually we still support only one region that is could be high or low, >> and that extra low is just for workaround >> buggy system that does not support iommu with kdump. > > Well, crashkernel=X;high crashkernel=Y;low will reserve two ranges (one > high and one low). So in some cases we are supporting 2 and in some > cases we are supporting 1 range. when you have more 4G ram or not. and when we have two ranges, low range actually is not for second kernel to be loaded. and it is only for swiotlb in case. > > So I still think that let us stick to old behavior of supporting one > crashkernel= option. Last crashkernel= option on command line will be > acted upon. Yes, only one crashkernel=;high and one crashkernel=;low is honored. -- 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