lkml.org 
[lkml]   [2014]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH] Fix northbridge quirk to assign correct NUMA node
    Date
    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>
    ---
    arch/x86/kernel/quirks.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/arch/x86/kernel/quirks.c b/arch/x86/kernel/quirks.c
    index 04ee1e2..52dbf1e 100644
    --- a/arch/x86/kernel/quirks.c
    +++ b/arch/x86/kernel/quirks.c
    @@ -529,7 +529,7 @@ static void quirk_amd_nb_node(struct pci_dev *dev)
    return;

    pci_read_config_dword(nb_ht, 0x60, &val);
    - node = val & 7;
    + node = pcibus_to_node(dev->bus) | (val & 7);
    /*
    * Some hardware may return an invalid node ID,
    * so check it first:
    --
    1.8.3.2


    \
     
     \ /
      Last update: 2014-03-13 13:21    [W:4.120 / U:0.500 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site