diff options
author | Daniel Borkmann <daniel@iogearbox.net> | 2017-02-21 16:09:33 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-02-21 13:30:13 -0500 |
commit | d2852a2240509e512712e25de2d0796cda435ecb (patch) | |
tree | 1a7b8c0311150eb57ab62857001f1895560200c8 /arch/mn10300/mm | |
parent | 559c59b238ebb7d39b732b6b08a59693b972e75c (diff) | |
download | linux-stable-d2852a2240509e512712e25de2d0796cda435ecb.tar.gz linux-stable-d2852a2240509e512712e25de2d0796cda435ecb.tar.bz2 linux-stable-d2852a2240509e512712e25de2d0796cda435ecb.zip |
arch: add ARCH_HAS_SET_MEMORY config
Currently, there's no good way to test for the presence of
set_memory_ro/rw/x/nx() helpers implemented by archs such as
x86, arm, arm64 and s390.
There's DEBUG_SET_MODULE_RONX and DEBUG_RODATA, however both
don't really reflect that: set_memory_*() are also available
even when DEBUG_SET_MODULE_RONX is turned off, and DEBUG_RODATA
is set by parisc, but doesn't implement above functions. Thus,
add ARCH_HAS_SET_MEMORY that is selected by mentioned archs,
where generic code can test against this.
This also allows later on to move DEBUG_SET_MODULE_RONX out of
the arch specific Kconfig to define it only once depending on
ARCH_HAS_SET_MEMORY.
Suggested-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/mn10300/mm')
0 files changed, 0 insertions, 0 deletions