diff options
| author | Matias Bjørling <[email protected]> | 2018-11-26 19:27:03 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2018-11-27 02:30:40 +0000 |
| commit | ef78e5ec9214376c5cb989f5da70b02d0c117b66 (patch) | |
| tree | d111e5e3d4565275b10f9394ac7da6a1389d1274 /tools/bpf/bpftool/prog.c | |
| parent | Merge tag 'hwmon-for-v4.20-rc5' of git://git.kernel.org/pub/scm/linux/kernel/... (diff) | |
| download | kernel-ef78e5ec9214376c5cb989f5da70b02d0c117b66.tar.gz kernel-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 <[email protected]>
Signed-off-by: Tony Luck <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/bpf/bpftool/prog.c')
0 files changed, 0 insertions, 0 deletions