libnvdimm, nfit: enable support for volatile ranges
authorDan Williams <dan.j.williams@intel.com>
Tue, 30 May 2017 06:12:19 +0000 (23:12 -0700)
committerDan Williams <dan.j.williams@intel.com>
Tue, 27 Jun 2017 23:44:13 +0000 (16:44 -0700)
commitc9e582aa689f5418ca30e1e7a975039772c3a757
tree34ea0b661819d2e80c80a2197ad264e55b0fffc6
parentc00b396ef782cb2296200d868a0013d8ca1d615e
libnvdimm, nfit: enable support for volatile ranges

Allow volatile nfit ranges to participate in all the same infrastructure
provided for persistent memory regions. A resulting resulting namespace
device will still be called "pmem", but the parent region type will be
"nd_volatile". This is in preparation for disabling the dax ->flush()
operation in the pmem driver when it is hosted on a volatile range.

Cc: Jan Kara <jack@suse.cz>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Matthew Wilcox <mawilcox@microsoft.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
drivers/acpi/nfit/core.c
drivers/nvdimm/bus.c
drivers/nvdimm/core.c
drivers/nvdimm/dax_devs.c
drivers/nvdimm/dimm_devs.c
drivers/nvdimm/namespace_devs.c
drivers/nvdimm/nd-core.h
drivers/nvdimm/pfn_devs.c
drivers/nvdimm/region_devs.c