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: Thu, 18 Aug 2016 11:15:10 -0700 From: Dan Williams <dan.j.williams@...el.com> To: Matthew Wilcox <mawilcox@...rosoft.com> Cc: Matthew Wilcox <mawilcox@...uxonhyperv.com>, X86 ML <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org> Subject: Re: [PATCH 1/2] x86: Set up resources correctly on Hyper-V Generation 2 On Thu, Aug 18, 2016 at 11:05 AM, Matthew Wilcox <mawilcox@...rosoft.com> wrote: > I'd rather the memmap= option works on all platforms. Unless we're going to get rid of it entirely and exclusively use ACPI tables, I see no good reason to leave this landmine lying around for someone else to blow their own leg off. > memmap= is already a landmine: https://lkml.org/lkml/2016/6/28/819 Killing memmap= in favor of NFIT is a better way to go. I chatted with Peter off list about this problem and he wondered about re-purposing using the mBFT mechanism to define memory ranges: http://omniboot.org/txt/syslinux/memdisk.txt
Powered by blists - more mailing lists