summaryrefslogtreecommitdiffstats
path: root/Documentation/spi/spi-lm70llp
diff options
context:
space:
mode:
authorLukasz Anaczkowski <lukasz.anaczkowski@intel.com>2016-04-21 11:29:00 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-04-21 22:13:03 +0200
commit702b07fcc9b264c9afd372676bbdd50a762dcde0 (patch)
treea92c009c3afe4b213ccb0da65cdd231dfcd7aff2 /Documentation/spi/spi-lm70llp
parentc3b46c73264b03000d1e18b22f5caf63332547c9 (diff)
downloadblackbird-op-linux-702b07fcc9b264c9afd372676bbdd50a762dcde0.tar.gz
blackbird-op-linux-702b07fcc9b264c9afd372676bbdd50a762dcde0.zip
ACPI / SRAT: fix SRAT parsing order with both LAPIC and X2APIC present
SRAT maps APIC ID to proximity domains ids (PXM). Mapping from PXM to NUMA node ids is based on order of entries in SRAT table. SRAT table has just LAPIC entires or mix of LAPIC and X2APIC entries. As long as there are only LAPIC entires, mapping from proximity domain id to NUMA node id is as assumed by BIOS. However, once APIC entries are mixed, X2APIC entries would be first mapped which causes unexpected NUMA node mapping. To fix that, change parsing to check each entry against both LAPIC and X2APIC so mapping is in the SRAT/PXM order. This is supplemental change to the fix made by commit d81056b5278 (Handle apic/x2apic entries in MADT in correct order) and using the mechanism introduced by 9b3fedd (ACPI / tables: Add acpi_subtable_proc to ACPI table parsers). Fixes: d81056b5278 (Handle apic/x2apic entries in MADT in correct order) Signed-off-by: Lukasz Anaczkowski <lukasz.anaczkowski@intel.com> [ rjw : Subject & changelog ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'Documentation/spi/spi-lm70llp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud