[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFxPn3J68MsqQd7OVv7jetZjPduP53MFmw2f_-z7=ebpXQ@mail.gmail.com>
Date: Tue, 8 Mar 2016 14:23:48 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Toshi Kani <toshi.kani@....com>, Ingo Molnar <mingo@...nel.org>,
Borislav Petkov <bp@...e.de>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2-UPDATE2 3/4] resource: Add device-managed insert/remove_resource()
On Tue, Mar 8, 2016 at 12:59 PM, Dan Williams <dan.j.williams@...el.com> wrote:
>
> Here's the usage patch from Toshi [1] (copied below). It is indeed a
> resource injected by nfit / nvdimm bus implementation. We just happen
> to support nfit and libnvdimm as modules.
>
> The goal of these patches is to use the ACPI NFIT data to create a
> "Persistent Memory" rather than "reserved" resource. This is for
> platform-firmware implementations that use E820-Type2 rather than
> E820-Type7 to describe pmem.
So my worry is that there is likely exactly one or two of these kinds of sites.
Why couldn't they just use insert_resource() and then remove it manually?
Linus
Powered by blists - more mailing lists