On Sun, Mar 22, 2020 at 5:28 PM Dan Williams <dan.j.willi...@intel.com> wrote: > > Changes since v1 : > - Kill the ifdef'ery in arch/x86/mm/numa.c (Rafael) > > - Add a dummy phys_to_target_node() for ARM64 (0day-robot) > > - Initialize ->child and ->sibling to NULL in the resource returned by > find_next_iomem_res() (Inspired by Tom's feedback even though it does > not set them like he suggested) > > - Collect Ard's Ack > > : > http://lore.kernel.org/r/158318759687.2216124.4684754859068906007.st...@dwillia2-desk3.amr.corp.intel.com > > --- > > My primary motivation is making the dax_kmem facility useful to > shipping platforms that have performance differentiated memory, but > may not have EFI-defined soft-reservations / HMAT (or > non-EFI-ACPI-platform equivalent). I'm anticipating HMAT enabled > platforms where the platform firmware policy for what is > soft-reserved, or not, is not the policy the system owner would pick. > I'd also highlight Joao's work  (see the TODO section) as an > indication of the demand for custom carving memory resources and > applying the device-dax memory management interface. > > Given the current dearth of systems that supply an ACPI HMAT table, and > the utility of being able to manually define device-dax "hmem" instances > via the efi_fake_mem= option, relax the requirements for creating these > devices. Specifically, add an option (numa=nohmat) to optionally disable > consideration of the HMAT and update efi_fake_mem= to behave like > memmap=nn!ss in terms of delimiting device boundaries. > > : > https://lore.kernel.org/lkml/20200110190313.17144-1-joao.m.mart...@oracle.com/ > > With Ard's and Rafael's ack I'd feel ok taking this through the nvdimm > tree, please holler if anything still needs some fixups.
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com> for the whole series. Thanks! _______________________________________________ Linux-nvdimm mailing list -- email@example.com To unsubscribe send an email to linux-nvdimm-le...@lists.01.org