summaryrefslogtreecommitdiff
path: root/lib/locking-selftest-wlock-softirq.h
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2022-09-28 18:45:17 +0300
committerCatalin Marinas <catalin.marinas@arm.com>2022-09-29 19:34:40 +0300
commit55c8a987dd73a7ef9e53119f3329620768d4a655 (patch)
tree023b8c5908939b5423878acc74da78c9fcb0c6ce /lib/locking-selftest-wlock-softirq.h
parent33060a64901e61f09ea6faffe367551df18a54c3 (diff)
downloadlinux-55c8a987dd73a7ef9e53119f3329620768d4a655.tar.xz
kselftest/arm64: Don't enable v8.5 for MTE selftest builds
Currently we set -march=armv8.5+memtag when building the MTE selftests, allowing the compiler to emit v8.5 and MTE instructions for anything it generates. This means that we may get code that will generate SIGILLs when run on older systems rather than skipping on non-MTE systems as should be the case. Most toolchains don't select any incompatible instructions but I have seen some reports which suggest that some may be appearing which do so. This is also potentially problematic in that if the compiler chooses to emit any MTE instructions for the C code it may interfere with the MTE usage we are trying to test. Since the only reason we are specifying this option is to allow us to assemble MTE instructions in mte_helper.S we can avoid these issues by moving to using a .arch directive there and adding the -march explicitly to the toolchain support check instead of the generic CFLAGS. Signed-off-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20220928154517.173108-1-broonie@kernel.org Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'lib/locking-selftest-wlock-softirq.h')
0 files changed, 0 insertions, 0 deletions