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: Mon, 05 Nov 2012 03:59:32 +0100 From: "H. Peter Anvin" <hpa@...or.com> To: "Zhang, Jun" <jun.zhang@...el.com> CC: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "x86@...nel.org" <x86@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, "Fleming, Matt" <matt.fleming@...el.com>, Paul Gortmaker <paul.gortmaker@...driver.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] crash dump: don't delete non-E820_RAM during init On 11/05/2012 03:57 AM, Zhang, Jun wrote: > Hello, Anvin > 1) use "memmap=exactmap", which remove all ranges include ram and non-ram range. So my first patch reserve the non-ram range. > 2)don't use " memmap=exactmap ", so it reserve all ranges. But we only need non-ram, so we need kernel to remove RAM, just as my second patch. Sorry, you have completely lost me now. You seem to be contradicting yourself from one message to another. -hpa -- 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