[lkml]   [2012]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectx2APIC and many-APIC systems...
Ingo, Suresh,

Commit a35fd28256e7736cc84af8931a16224f0bfaaf6c prevents x2APIC
structures being used from the ACPI MADT if the cores don't advertise
the x2APIC feature. Commit c284b42abadbb22083bfde24d308899c08d44ffa
prevents onlining cores with APIC ID >255 in non-x2APIC mode. Since
NumaChip/NumaConnect uses x2APIC structures to describe non-x2APIC
systems (AMD Opteron) with lots of APICs, we thus now can't boot all the

We are able to set the x2APIC bit in the processor feature flags, so get
caught by the second patch. Is there an appropriate approach to use in
these circumstances? Otherwise, would a patch that separates the APIC ID
handover and future x2APIC MSR access be appropriate?

Many thanks,
Daniel J Blueman
Principal Software Engineer, Numascale Asia

 \ /
  Last update: 2012-03-13 10:31    [W:0.089 / U:35.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site