diff options
author | Dan Williams <dan.j.williams@intel.com> | 2018-03-21 15:12:07 -0700 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2018-03-21 15:12:07 -0700 |
commit | fe9a552e715dfe5167d52deb74ea16335896bdaf (patch) | |
tree | f47ac26b9a82ebde8c4a1380fe1ea1571e52ac3b /arch | |
parent | 896196dc4e419a9d0782404e0befac17d638fc01 (diff) | |
download | linux-fe9a552e715dfe5167d52deb74ea16335896bdaf.tar.bz2 |
libnvdimm, nfit: fix persistence domain reporting
The persistence domain is a point in the platform where once writes
reach that destination the platform claims it will make them persistent
relative to power loss. In the ACPI NFIT this is currently communicated
as 2 bits in the "NFIT - Platform Capabilities Structure". The bits
comprise a hierarchy, i.e. bit0 "CPU Cache Flush to NVDIMM Durability on
Power Loss Capable" implies bit1 "Memory Controller Flush to NVDIMM
Durability on Power Loss Capable".
Commit 96c3a239054a "libnvdimm: expose platform persistence attr..."
shows the persistence domain as flags, but it's really an enumerated
hierarchy.
Fix this newly introduced user ABI to show the closest available
persistence domain before userspace develops dependencies on seeing, or
needing to develop code to tolerate, the raw NFIT flags communicated
through the libnvdimm-generic region attribute.
Fixes: 96c3a239054a ("libnvdimm: expose platform persistence attr...")
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions