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)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 1 Apr 2014 23:58:59 +0000 (00:58 +0100)
commitb10349aded21e5cab89ab99cbc2aa90d00314ee6
tree2ba566cff2ac295ebe050ca4ab2ca797036dbe8f
parentcd840143ae1bd82d1fe37914956198b24235c3a9
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: Ben Hutchings <ben@decadent.org.uk>
arch/x86/kernel/quirks.c