Messages in this thread | | | From | Matthew Wilcox <> | Subject | RE: [PATCH 1/2] x86: Set up resources correctly on Hyper-V Generation 2 | Date | Thu, 18 Aug 2016 18:26:17 +0000 |
| |
*Until* such a mechanism is in, I see no reason to not keep feature parity for all platforms. This is the exact "You should boil the ocean" response that Arjan famously complained about at Kernel Summit a few years ago.
-----Original Message----- From: Dan Williams [mailto:dan.j.williams@intel.com] Sent: Thursday, August 18, 2016 2:15 PM To: Matthew Wilcox <mawilcox@microsoft.com> Cc: Matthew Wilcox <mawilcox@linuxonhyperv.com>; X86 ML <x86@kernel.org>; linux-kernel@vger.kernel.org; linux-nvdimm@lists.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@microsoft.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
| |