x86/amd/numa: Fix northbridge quirk to assign correct NUMA node
authorDaniel J Blueman <daniel@numascale.com>
Thu, 13 Mar 2014 11:43:01 +0000 (19:43 +0800)
committerJiri Slaby <jslaby@suse.cz>
Sat, 22 Mar 2014 21:01:54 +0000 (22:01 +0100)
commite108610d6dcb947d4a8743f8f5bcfb008982826f
tree4b66a5ac3f83a6a2483505e0d2e8def31f815cc5
parentf4592be7d7d62c137999e058288618398fe2babc
x86/amd/numa: Fix northbridge quirk to assign correct NUMA node

commit 847d7970defb45540735b3fb4e88471c27cacd85 upstream.

For systems with multiple servers and routed fabric, all
northbridges get assigned to the first server. Fix this by also
using the node reported from the PCI bus. For single-fabric
systems, the northbriges are on PCI bus 0 by definition, which
are on NUMA node 0 by definition, so this is invarient on most
systems.

Tested on fam10h and fam15h single and multi-fabric systems and
candidate for stable.

Signed-off-by: Daniel J Blueman <daniel@numascale.com>
Acked-by: Steffen Persvold <sp@numascale.com>
Acked-by: Borislav Petkov <bp@suse.de>
Link: http://lkml.kernel.org/r/1394710981-3596-1-git-send-email-daniel@numascale.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
arch/x86/kernel/quirks.c