diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2016-04-15 05:40:47 +0300 |
|---|---|---|
| committer | Ross Zwisler <ross.zwisler@linux.intel.com> | 2016-04-15 23:59:41 +0300 |
| commit | 0a370d261c805286cbdfa1f96661322a28cce860 (patch) | |
| tree | 11035c733e2e9b0d6e33f181ae9b99aba22a3fac /include | |
| parent | cba2e47abcbd80e3f46f460899290402f98090ec (diff) | |
| download | linux-0a370d261c805286cbdfa1f96661322a28cce860.tar.xz | |
libnvdimm, pmem: clarify the write+clear_poison+write flow
The ACPI specification does not specify the state of data after a clear
poison operation. Potential future libnvdimm bus implementations for
other architectures also might not specify or disagree on the state of
data after clear poison. Clarify why we write twice.
Reported-by: Jeff Moyer <jmoyer@redhat.com>
Reported-by: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions