aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/dma-mapping.h
diff options
context:
space:
mode:
authorMatias Bjørling <mb@lightnvm.io>2018-11-26 11:27:03 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2018-11-26 18:30:40 -0800
commitef78e5ec9214376c5cb989f5da70b02d0c117b66 (patch)
treed111e5e3d4565275b10f9394ac7da6a1389d1274 /include/linux/dma-mapping.h
parentMerge tag 'hwmon-for-v4.20-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (diff)
downloadwireguard-linux-ef78e5ec9214376c5cb989f5da70b02d0c117b66.tar.xz
wireguard-linux-ef78e5ec9214376c5cb989f5da70b02d0c117b66.zip
ia64: export node_distance function
The numa_slit variable used by node_distance is available to a module as long as it is linked at compile-time. However, it is not available to loadable modules. Leading to errors such as: ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefined! The error above is caused by the nvme multipath code that makes use of node_distance for its path calculation. When the patch was added, the lightnvm subsystem would select nvme and always compile it in, leading to the node_distance call to always succeed. However, when this requirement was removed, nvme could be compiled in as a module, which exposed this bug. This patch extracts node_distance to a function and exports it. Since ACPI is depending on node_distance being a simple lookup to numa_slit, the previous behavior is exposed as slit_distance and its users updated. Fixes: f333444708f82 "nvme: take node locality into account when selecting a path" Fixes: 73569e11032f "lightnvm: remove dependencies on BLK_DEV_NVME and PCI" Signed-off-by: Matias Bjøring <mb@lightnvm.io> Signed-off-by: Tony Luck <tony.luck@intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/dma-mapping.h')
0 files changed, 0 insertions, 0 deletions