diff options
author | Toshi Kani <toshi.kani@hp.com> | 2014-01-21 14:33:15 -0800 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2014-01-25 09:13:35 +0100 |
commit | a85eba8814631d0d48361c8b9a7ee0984e80c03c (patch) | |
tree | 3345d54be0db08bac7bf8f00cbd95d2fa72abcac /lib/Kconfig.debug | |
parent | b9a3b4c976c1209957326537ad5c0bb633dfd764 (diff) | |
download | talos-obmc-linux-a85eba8814631d0d48361c8b9a7ee0984e80c03c.tar.gz talos-obmc-linux-a85eba8814631d0d48361c8b9a7ee0984e80c03c.zip |
arch/x86/mm/srat: Skip NUMA_NO_NODE while parsing SLIT
When ACPI SLIT table has an I/O locality (i.e. a locality
unique to an I/O device), numa_set_distance() emits this warning
message:
NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10
acpi_numa_slit_init() calls numa_set_distance() with
pxm_to_node(), which assumes that all localities have been
parsed with SRAT previously. SRAT does not list I/O localities,
where as SLIT lists all localities including I/Os. Hence,
pxm_to_node() returns NUMA_NO_NODE (-1) for an I/O locality.
I/O localities are not supported and are ignored today, but emitting
such warning message leads to unnecessary confusion.
Change acpi_numa_slit_init() to avoid calling
numa_set_distance() with NUMA_NO_NODE.
Signed-off-by: Toshi Kani <toshi.kani@hp.com>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Link: http://lkml.kernel.org/n/tip-dSvpjjvp8aMzs1ybkftxohlh@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'lib/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions