> -----Original Message----- > From: Linux-nvdimm [mailto:linux-nvdimm-bounces@xxxxxxxxxxxx] On > Behalf Of Dan Williams > Sent: Friday, June 10, 2016 9:28 AM > To: Yigal Korman <yigal@xxxxxxxxxxxxx> > Cc: Matt Fleming <matt@xxxxxxxxxxxxxxxxxxx>; linux- > efi@xxxxxxxxxxxxxxx; linux-nvdimm@xxxxxxxxxxxx > Subject: Re: [PATCH] efi: kernel param for legacy NVDIMM support > > On Fri, Jun 10, 2016 at 1:48 AM, Yigal Korman <yigal@xxxxxxxxxxxxx> > wrote: > > On Thu, Jun 9, 2016 at 11:27 PM, Dan Williams ... > We should always look for an NFIT in the type-14 case. Injecting a > crafted NFIT for this legacy case removes confusion as there is only > one action the kernel takes and no possibility for collisions. I > also > do not want to make it easier for firmware developers to skip the > necessary due diligence to decide whether attributes like numa > topology, posted write queue flush mechanisms, and media health, > etc... need description. I'll also reiterate that NVDIMM ranges may also be reported using the UEFI and E820 reserved types. The simple E820 and UEFI memory map persistent memory type values do not contain enough information to properly talk to an NVDIMM; the information in ACPI NFIT is crucial. --- Robert Elliott, HPE Persistent Memory -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
