diff options
| author | Robin Murphy <robin.murphy@arm.com> | 2017-08-31 12:27:09 +0100 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2017-08-31 15:05:10 -0700 |
| commit | 5deb67f77a266010e2c10fb124b7516d0d258ce8 (patch) | |
| tree | 23d02b63d21e943145f2720460b32b301fefbca4 /lib | |
| parent | d9b83c7569536e3255992491737d9f895640ea18 (diff) | |
| download | linux-5deb67f77a266010e2c10fb124b7516d0d258ce8.tar.bz2 | |
libnvdimm, nd_blk: remove mmio_flush_range()
mmio_flush_range() suffers from a lack of clearly-defined semantics,
and is somewhat ambiguous to port to other architectures where the
scope of the writeback implied by "flush" and ordering might matter,
but MMIO would tend to imply non-cacheable anyway. Per the rationale
in 67a3e8fe9015 ("nd_blk: change aperture mapping from WC to WB"), the
only existing use is actually to invalidate clean cache lines for
ARCH_MEMREMAP_PMEM type mappings *without* writeback. Since the recent
cleanup of the pmem API, that also now happens to be the exact purpose
of arch_invalidate_pmem(), which would be a far more well-defined tool
for the job.
Rather than risk potentially inconsistent implementations of
mmio_flush_range() for the sake of one callsite, streamline things by
removing it entirely and instead move the ARCH_MEMREMAP_PMEM related
definitions up to the libnvdimm level, so they can be shared by NFIT
as well. This allows NFIT to be enabled for arm64.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/Kconfig | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/lib/Kconfig b/lib/Kconfig index 6762529ad9e4..527da69e3be1 100644 --- a/lib/Kconfig +++ b/lib/Kconfig @@ -559,9 +559,6 @@ config ARCH_HAS_PMEM_API config ARCH_HAS_UACCESS_FLUSHCACHE bool -config ARCH_HAS_MMIO_FLUSH - bool - config STACKDEPOT bool select STACKTRACE |