[PATCH v2] UefiPayloadPkg: Correct MAX_LOGICAL_PROCESSORS value

[PATCH v2] UefiPayloadPkg: Correct MAX_LOGICAL_PROCESSORS value

[Xiaoqiang Zhang]

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4367

Issue:
For Server platforms, when FSP does not output mCpuInitMpLibHobGuid HOB,
the code will wakeup all APs and calculate the processor count in DXE
phase. But when processor thread number is above 256, will encounter
Startup IPI exception in DXE phase.

Root cause:
MAX_LOGICAL_PROCESSORS MARCO value in UefiPayloadPkg.dsc is 256,
when the actual processor thread number is above 256, will encounter
data overflow exception.

Solution:
Align MAX_LOGICAL_PROCESSORS value with Server platform side value 1024.

Signed-off-by: Xiaoqiang Zhang <xiaoqiang.zhang@intel.com>
Cc: Guo Dong <guo.dong@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: James Lu <james.lu@intel.com>
---
 UefiPayloadPkg/UefiPayloadPkg.dsc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/UefiPayloadPkg/UefiPayloadPkg.dsc b/UefiPayloadPkg/UefiPayloadPkg.dsc
index 35e3bfff35..bca5d3f335 100644
--- a/UefiPayloadPkg/UefiPayloadPkg.dsc
+++ b/UefiPayloadPkg/UefiPayloadPkg.dsc
@@ -59,7 +59,7 @@
   #
   # CPU options
   #
-  DEFINE MAX_LOGICAL_PROCESSORS       = 256
+  DEFINE MAX_LOGICAL_PROCESSORS       = 1024
 
   #
   # PCI options
-- 
2.39.1.windows.1

Re: [PATCH v2] UefiPayloadPkg: Correct MAX_LOGICAL_PROCESSORS value

[Lu, James]

Reviewed-by: James Lu <james.lu@intel.com>


Thanks,
James

-----Original Message-----
From: Zhang, Xiaoqiang <xiaoqiang.zhang@intel.com> 
Sent: Monday, March 13, 2023 12:53 PM
To: devel@edk2.groups.io
Cc: Zhang, Xiaoqiang <xiaoqiang.zhang@intel.com>; Dong, Guo <guo.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Lu, James <james.lu@intel.com>
Subject: [PATCH v2] UefiPayloadPkg: Correct MAX_LOGICAL_PROCESSORS value

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4367

Issue:
For Server platforms, when FSP does not output mCpuInitMpLibHobGuid HOB, the code will wakeup all APs and calculate the processor count in DXE phase. But when processor thread number is above 256, will encounter Startup IPI exception in DXE phase.

Root cause:
MAX_LOGICAL_PROCESSORS MARCO value in UefiPayloadPkg.dsc is 256, when the actual processor thread number is above 256, will encounter data overflow exception.

Solution:
Align MAX_LOGICAL_PROCESSORS value with Server platform side value 1024.

Signed-off-by: Xiaoqiang Zhang <xiaoqiang.zhang@intel.com>
Cc: Guo Dong <guo.dong@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: James Lu <james.lu@intel.com>
---
 UefiPayloadPkg/UefiPayloadPkg.dsc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/UefiPayloadPkg/UefiPayloadPkg.dsc b/UefiPayloadPkg/UefiPayloadPkg.dsc
index 35e3bfff35..bca5d3f335 100644
--- a/UefiPayloadPkg/UefiPayloadPkg.dsc
+++ b/UefiPayloadPkg/UefiPayloadPkg.dsc
@@ -59,7 +59,7 @@
   #
   # CPU options
   #
-  DEFINE MAX_LOGICAL_PROCESSORS       = 256
+  DEFINE MAX_LOGICAL_PROCESSORS       = 1024
 
   #
   # PCI options
--
2.39.1.windows.1