From fb28799ed51134ae4646306d3abe2b7f3287a0e9 Mon Sep 17 00:00:00 2001 From: Subrata Banik Date: Sun, 24 Jul 2022 11:19:04 +0530 Subject: [PATCH] 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 Change-Id: I466e6cc568024a9dea80af21e0ebf3572e74a1f1 Reviewed-on: https://review.coreboot.org/c/coreboot/+/66110 Tested-by: build bot (Jenkins) Reviewed-by: Angel Pons Reviewed-by: Felix Held --- src/cpu/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cpu/x86/Kconfig b/src/cpu/x86/Kconfig index 80b9a44c99..8d76638ff9 100644 --- a/src/cpu/x86/Kconfig +++ b/src/cpu/x86/Kconfig @@ -60,7 +60,7 @@ config X2APIC_RUNTIME config X2APIC_LATE_WORKAROUND prompt "Use XAPIC for AP bringup, then change to X2APIC" bool - depends on PARALLEL_MP && MAX_CPUS < 255 + depends on PARALLEL_MP && MAX_CPUS < 256 help Choose this option if the platform supports dynamic switching between XAPIC to X2APIC. The initial Application Processors (APs) are configured