forked from Minki/linux
e511c4a3d2
Up till now, dax_direct_access() is used implicitly for normal
access, but for the purpose of recovery write, dax range with
poison is requested. To make the interface clear, introduce
enum dax_access_mode {
DAX_ACCESS,
DAX_RECOVERY_WRITE,
}
where DAX_ACCESS is used for normal dax access, and
DAX_RECOVERY_WRITE is used for dax recovery write.
Suggested-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Jane Chu <jane.chu@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Cc: Mike Snitzer <snitzer@redhat.com>
Reviewed-by: Vivek Goyal <vgoyal@redhat.com>
Link: https://lore.kernel.org/r/165247982851.52965.11024212198889762949.stgit@dwillia2-desk3.amr.corp.intel.com
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
||
|---|---|---|
| .. | ||
| test | ||
| acpi_nfit_test.c | ||
| config_check.c | ||
| dax_pmem_test.c | ||
| dax-dev.c | ||
| device_dax_test.c | ||
| dimm_devs.c | ||
| Kbuild | ||
| libnvdimm_test.c | ||
| Makefile | ||
| pmem_test.c | ||
| pmem-dax.c | ||
| watermark.h | ||