summaryrefslogtreecommitdiffstats
path: root/drivers/iommu/io-pgtable-arm-v7s.c
diff options
context:
space:
mode:
authorWill Deacon <will.deacon@arm.com>2017-06-23 11:45:57 +0100
committerWill Deacon <will.deacon@arm.com>2017-06-23 17:58:02 +0100
commitc1004803b40596c1aabbbc78a6b1b33e4dfd96c6 (patch)
tree351de9d04fb88b9e2b9121080ca0a67bd859a53d /drivers/iommu/io-pgtable-arm-v7s.c
parent58188afeb727e0f73706f1460707bd3ba6ccc221 (diff)
downloadlinux-stable-c1004803b40596c1aabbbc78a6b1b33e4dfd96c6.tar.gz
linux-stable-c1004803b40596c1aabbbc78a6b1b33e4dfd96c6.tar.bz2
linux-stable-c1004803b40596c1aabbbc78a6b1b33e4dfd96c6.zip
iommu/io-pgtable: depend on !GENERIC_ATOMIC64 when using COMPILE_TEST with LPAE
The LPAE/ARMv8 page table format relies on the ability to read and write 64-bit page table entries in an atomic fashion. With the move to a lockless implementation, we also need support for cmpxchg64 to resolve races when installing table entries concurrently. Unfortunately, not all architectures support cmpxchg64, so the code can fail to compiler when building for these architectures using COMPILE_TEST. Rather than disable COMPILE_TEST altogether, instead check that GENERIC_ATOMIC64 is not selected, which is a reasonable indication that the architecture has support for 64-bit cmpxchg. Reported-by: kbuild test robot <fengguang.wu@intel.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'drivers/iommu/io-pgtable-arm-v7s.c')
0 files changed, 0 insertions, 0 deletions