diff options
| author | Vishal Verma <vishal.l.verma@intel.com> | 2018-06-18 17:17:02 -0600 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2018-06-30 10:45:48 -0700 |
| commit | 1273c253c32b9a073a4d8921ed079177ccc7c8af (patch) | |
| tree | 6c7f47ce4bd1a4535abc66f9fcf02ddbd8be6ddf /tools/testing/nvdimm/test/nfit.c | |
| parent | c1985cefd844e26bd19673a6df8d8f0b1918c2db (diff) | |
| download | linux-1273c253c32b9a073a4d8921ed079177ccc7c8af.tar.gz linux-1273c253c32b9a073a4d8921ed079177ccc7c8af.tar.bz2 linux-1273c253c32b9a073a4d8921ed079177ccc7c8af.zip | |
tools/testing/nvdimm: advertise a write cache for nfit_test
Commit 546eb0317cfa "libnvdimm, pmem: Do not flush power-fail protected CPU caches"
fixed the write_cache detection to correctly show the lack of a write
cache based on the platform capabilities described in the ACPI NFIT. The
nfit_test unit tests expected a write cache to be present, so change the
nfit test namespaces to only advertise a persistence domain limited to
the memory controller. This allows the kernel to show a write_cache
attribute, and the test behaviour remains unchanged.
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'tools/testing/nvdimm/test/nfit.c')
| -rw-r--r-- | tools/testing/nvdimm/test/nfit.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/tools/testing/nvdimm/test/nfit.c b/tools/testing/nvdimm/test/nfit.c index a8fb63edcf89..e2926f72a821 100644 --- a/tools/testing/nvdimm/test/nfit.c +++ b/tools/testing/nvdimm/test/nfit.c @@ -1991,8 +1991,7 @@ static void nfit_test0_setup(struct nfit_test *t) pcap->header.type = ACPI_NFIT_TYPE_CAPABILITIES; pcap->header.length = sizeof(*pcap); pcap->highest_capability = 1; - pcap->capabilities = ACPI_NFIT_CAPABILITY_CACHE_FLUSH | - ACPI_NFIT_CAPABILITY_MEM_FLUSH; + pcap->capabilities = ACPI_NFIT_CAPABILITY_MEM_FLUSH; offset += pcap->header.length; if (t->setup_hotplug) { |