Message ID | BLU437-SMTP1028FC9A1CD343086DA05ECBFBB0@phx.gbl |
---|---|
State | Accepted |
Delegated to: | Simon Glass |
Headers | show |
On 12 June 2015 at 00:52, Bin Meng <bmeng.cn@gmail.com> wrote: > MAX_CPUS and AP_STACK_SIZE are only meaningful when SMP is on. > > Signed-off-by: Bin Meng <bmeng.cn@gmail.com> > Acked-by: Simon Glass <sjg@chromium.org> > --- > > Changes in v2: None > > arch/x86/Kconfig | 2 ++ > 1 file changed, 2 insertions(+) Applied to u-boot-x86.
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 3506ba2..d4cd9ed 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -228,6 +228,7 @@ config FSP_TEMP_RAM_ADDR config MAX_CPUS int "Maximum number of CPUs permitted" + depends on SMP default 4 help When using multi-CPU chips it is possible for U-Boot to start up @@ -249,6 +250,7 @@ config SMP config AP_STACK_SIZE hex + depends on SMP default 0x1000 help Each additional CPU started by U-Boot requires its own stack. This