On Fri, Oct 9, 2015 at 11:08 AM, Verma, Vishal L <vishal.l.verma@xxxxxxxxx> wrote: > On Fri, 2015-10-09 at 13:33 -0400, Jeff Moyer wrote: >> Vishal Verma <vishal.l.verma@xxxxxxxxx> writes: >> >> > Add a .notify callback to the acpi_nfit_driver that gets called on >> > a >> > hotplug event. From this, evaluate the _FIT ACPI method which >> > returns >> > the updated NFIT with handles for the hot-plugged NVDIMM. >> > >> > Iterate over the new NFIT, and add any new tables found, and >> > register/enable the corresponding regions. >> > >> > In the nfit test framework, after normal initialization, update the >> > NFIT >> > with a new hot-plugged NVDIMM, and directly call into the driver to >> > update its view of the available regions. >> >> OK, so just plugging in new NVDIMMs is supported, right? Are there >> plans to support unplugging DIMMs? > > Right, this is hot-add only until someone has a hot-remove use case. > ...someone meaning ACPI, since it only defines a hot-add flow. We could prototype something for the virtualization provisioning use case, but it's not part of the current spec. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
