summaryrefslogtreecommitdiff
path: root/net/ieee802154/Kconfig
diff options
context:
space:
mode:
authorMax Filippov <jcmvbkbc@gmail.com>2017-01-31 18:35:37 -0800
committerMax Filippov <jcmvbkbc@gmail.com>2017-01-31 18:49:59 -0800
commit4b3e6f2ef3722f1a6a97b6034ed492c1a21fd4ae (patch)
tree8d7f85ac726d7b702732c8d0921cafc4bb6809cb /net/ieee802154/Kconfig
parent69973b830859bc6529a7a0468ba0d80ee5117826 (diff)
xtensa: fix noMMU build on cores with MMU
Commit bf15f86b343ed8 ("xtensa: initialize MMU before jumping to reset vector") calls MMU management functions even when CONFIG_MMU is not selected. That breaks noMMU build on cores with MMU. Don't manage MMU when CONFIG_MMU is not selected. Cc: stable@vger.kernel.org Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Diffstat (limited to 'net/ieee802154/Kconfig')
0 files changed, 0 insertions, 0 deletions
and invalidate_mapping_pages() just delete all exceptional radix tree entries they find. For DAX this is not desirable as we track cache dirtiness in these entries and when they are evicted, we may not flush caches although it is necessary. This can for example manifest when we write to the same block both via mmap and via write(2) (to different offsets) and fsync(2) then does not properly flush CPU caches when modification via write(2) was the last one. Create appropriate DAX functions to handle invalidation of DAX entries for invalidate_inode_pages2_range() and invalidate_mapping_pages() and wire them up into the corresponding mm functions. Acked-by: Johannes Weiner <hannes@cmpxchg.org> Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'tools/perf/Documentation/examples.txt')