summaryrefslogtreecommitdiffstats
path: root/include/rdma
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2017-10-06 09:13:46 +0200
committerDoug Ledford <dledford@redhat.com>2017-10-10 10:49:44 -0400
commit9cc12ad6db55d7d902260fead28a91710dd5dbe5 (patch)
tree5516b9a7c5ce18ca26a6d965d4ec04b725a26d3c /include/rdma
parent6b9f8970cd30929cb6b372fa44fa66da9e59c650 (diff)
downloadlinux-9cc12ad6db55d7d902260fead28a91710dd5dbe5.tar.bz2
infiniband: add MMU dependency for user_mem
The infiniband subsystem causes a link failure when the umem driver is built on MMU-less systems: mm/mmu_notifier.o: In function `do_mmu_notifier_register': mmu_notifier.c:(.text+0x32): undefined reference to `mm_take_all_locks' drivers/infiniband/core/umem.o: In function `ib_umem_get': umem.c:(.text+0x132): undefined reference to `can_do_mlock' drivers/infiniband/core/umem_odp.o: In function `ib_umem_odp_map_dma_pages': umem_odp.c:(.text+0x766): undefined reference to `get_user_pages_remote' This bug has existed for a while but only become apparent in ARM randconfig builds when the dependency on PCI was lifted, as none of the ARM-NOMMU targets support PCI at the moment. We could probably get the umem driver to build by providing an alternative implementation 'can_do_mlock()' that returns false on NOMMU-systems, but then we'd still have a problem with the mmu-notifiers required by CONFIG_INFINIBAND_ON_DEMAND_PAGING, so simply forbidding umem with NOMMU seems like the simplest workaround. Fixes: 931bc0d91639 ("IB: Move PCI dependency from root KConfig to HW's KConfigs") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'include/rdma')
0 files changed, 0 insertions, 0 deletions