arch/x86: Fix MAX_CPUS check proper for late X2APIC config

The X2APIC_LATE_WORKAROUND kconfig allows bringing APs in XAPIC mode initially hence, it won't work if LAPIC ID is > 0xff.

This patch ensures the MAX_CPUS logic is appropriate while selecting X2APIC_LATE_WORKAROUND kconfig from SoC.

BUG=b:219061518, b:219053812
TEST=Able to build Google/Rex.

Signed-off-by: Subrata Banik <subratabanik@google.com>
Change-Id: I466e6cc568024a9dea80af21e0ebf3572e74a1f1
Reviewed-on: https://review.coreboot.org/c/coreboot/+/66110
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-by: Felix Held <felix-coreboot@felixheld.de>
This commit is contained in:
Subrata Banik 2022-07-24 11:19:04 +05:30 committed by Felix Held
parent 4b31af493d
commit fb28799ed5
1 changed files with 1 additions and 1 deletions

View File

@ -60,7 +60,7 @@ config X2APIC_RUNTIME
config X2APIC_LATE_WORKAROUND config X2APIC_LATE_WORKAROUND
prompt "Use XAPIC for AP bringup, then change to X2APIC" prompt "Use XAPIC for AP bringup, then change to X2APIC"
bool bool
depends on PARALLEL_MP && MAX_CPUS < 255 depends on PARALLEL_MP && MAX_CPUS < 256
help help
Choose this option if the platform supports dynamic switching between Choose this option if the platform supports dynamic switching between
XAPIC to X2APIC. The initial Application Processors (APs) are configured XAPIC to X2APIC. The initial Application Processors (APs) are configured