summaryrefslogtreecommitdiffstats
path: root/include/acpi
diff options
context:
space:
mode:
authorJesse Barnes <jbarnes@virtuousgeek.org>2009-07-10 14:04:30 -0700
committerJesse Barnes <jbarnes@virtuousgeek.org>2009-09-09 13:29:21 -0700
commit2547089ca2db132e307ef68848ba029a8ec2f341 (patch)
treedb0079b322f964287571644c8376eb49bfcc68b7 /include/acpi
parenteaa959df299157e2640fcb3321537501b6afd9e6 (diff)
downloadlinux-2547089ca2db132e307ef68848ba029a8ec2f341.tar.gz
linux-2547089ca2db132e307ef68848ba029a8ec2f341.tar.bz2
linux-2547089ca2db132e307ef68848ba029a8ec2f341.zip
x86/PCI: initialize PCI bus node numbers early
The current mp_bus_to_node array is initialized only by AMD specific code, since AMD platforms have registers that can be used for determining mode numbers. On new Intel platforms it's necessary to initialize this array as well though, otherwise all PCI node numbers will be 0, when in fact they should be -1 (indicating that I/O isn't tied to any particular node). So move the mp_bus_to_node code into the common PCI code, and initialize it early with a default value of -1. This may be overridden later by arch code (e.g. the AMD code). With this change, PCI consistent memory and other node specific allocations (e.g. skbuff allocs) should occur on the "current" node. If, for performance reasons, applications want to be bound to specific nodes, they should open their devices only after being pinned to the CPU where they'll run, for maximum locality. Acked-by: Yinghai Lu <yinghai@kernel.org> Tested-by: Jesse Brandeburg <jesse.brandeburg@gmail.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'include/acpi')
0 files changed, 0 insertions, 0 deletions