[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM2PR21MB00898300C1E6F6761AC2ECD1CB150@DM2PR21MB0089.namprd21.prod.outlook.com>
Date: Thu, 18 Aug 2016 18:05:01 +0000
From: Matthew Wilcox <mawilcox@...rosoft.com>
To: Dan Williams <dan.j.williams@...el.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
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.
-----Original Message-----
From: Dan Williams [mailto:dan.j.williams@...el.com]
Sent: Thursday, August 18, 2016 2:03 PM
To: Matthew Wilcox <mawilcox@...rosoft.com>
Cc: Matthew Wilcox <mawilcox@...uxonhyperv.com>; 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 10:50 AM, Matthew Wilcox <mawilcox@...rosoft.com> wrote:
> This is the memmap= kernel command line option.
The Hyper-V ACPI tables are growing NFIT support, or I believe that work is already underway. I'd rather not touch the Linux PCI core to cover for the fact that Hyper-V disables one of the kernel's debug command line options when there's a platform standard way to communicate these resources.
Powered by blists - more mailing lists