Nate, I agree that MODE 3 mainly makes sense for systems with 64-bit PEI, since only a limited number of PCI segments and MMIO space can fit below the 4GB boundary. On most of our large systems, only

Mateusz, Your changes provide a nice cleanup to the driver mess in PEI. My main concern is that someone will later add a dependency which *requires* PCIe enumeration in PEI, without realizing that thi

Mateusz, Thank you for your enumeration of platform types, that helps clarify the discussion. Most servers I'm familiar with would fall in category 1. Large servers can't fit the entire PCIe config sp

Mateusz, Unfortunately, the continued migration of DXE code into PEI (specifically, into PEI code running before RAM is available) is putting a huge crunch on BIOS size. Server processors have a limit

I use cscope, and the "rscope" extension to emacs. I use a script to collect source files and include directories from the source tree to generate the cscope.files file. That works, but isn't smart ab

Thanks for the link. I agree that this change will make the StatusCodeHandler driver more modular, and is a step in the right direction. But I think it could go further, with almost no additional work

Dandan, The Status Code Protocol/PPI is the high-level interface which is being implemented. The ReportStatusCodeRouter module implements this in terms of the ReportStatusCodeHandler Protocol/PPI. Tha

Dandan, We'll have a lot of layers of indirection.... The ReportStatusCodeRouter modules will call one or more StatusCodeHandlerModules, and the standard StatusCodeHandler modules will call multiple S

Thank you. I agree with Laszlo: MP initialization is tricky to scale, and platform dependent. My group builds real machines with thousands of APs, and we have had to do various tweaks to the MP init.