[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM2PR21MB0089B1DD11FCF8453E518678CB150@DM2PR21MB0089.namprd21.prod.outlook.com>
Date: Thu, 18 Aug 2016 19:56:26 +0000
From: Matthew Wilcox <mawilcox@...rosoft.com>
To: Dan Williams <dan.j.williams@...el.com>
CC: 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
Compared to a patch which removes 5 lines of code, almost any additional work is ocean-boiling.
-----Original Message-----
From: Dan Williams [mailto:dan.j.williams@...el.com]
Sent: Thursday, August 18, 2016 3:12 PM
To: Matthew Wilcox <mawilcox@...rosoft.com>
Cc: X86 ML <x86@...nel.org>; linux-kernel@...r.kernel.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:26 AM, Matthew Wilcox <mawilcox@...rosoft.com> wrote:
> *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.
Feature parity for all platforms is the NFIT which Hyper-V is already implementing.
Setting that aside, if we want to fix memmap= for the general case, implementing a table like mBFT does not amount to ocean boiling in my opinion.
Powered by blists - more mailing lists