Jordan, CPU ID only could get the max logical processor number supported in current socket. It cannot handle multi-sockets case.
Yes. We could promote PcdCpuMaxLogicalProcessorNumber to dynamic type. But we need find one reliable way like you said to set it before CPU MP PEI not only CPU MP DXE. Thanks! Jeff -----Original Message----- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Jordan Justen Sent: Thursday, October 22, 2015 5:42 AM To: Kinney, Michael D; Laszlo Ersek; Kinney, Michael D Cc: Alex Williamson; edk2-de...@ml01.01.org; Xiao Guangrong; Eduardo Habkost Subject: Re: [edk2] [PATCH] OvmfPkg: increase MP services startup timeout On 2015-10-21 14:19:40, Kinney, Michael D wrote: > Laszlo, > > We have the PCD that specifies the max CPUs. > > ## Specifies max supported number of Logical Processors. > # @Prompt Configure max supported number of Logical Processors > > gUefiCpuPkgTokenSpaceGuid.PcdCpuMaxLogicalProcessorNumber|64|UINT32|0x > 00000002 It would need to be changed to a dynamic PCD. In terms of determining the number of logical processors, can't the cpuid function help? I'm not sure how QEMU handles that though. (Vaguely I remember something like cpuid only help with a single core... So, if QEMU presents as multiple cores, then maybe it can't help.) We'd need a reliable way to set the PCD before CpuDxe runs. -Jordan > We could exit the wait loop as soon as the number of detected CPUs > matches PcdCpuMaxLogicalProcessorNumber. _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
