I don't see that PEI-less boot is required for that. Sure, when stripping down
No. I have to say PEI-less boot in Config-B is a hard requirement.I'm still wondering why though. I have not yet seen a reason why
config-b can't use the PEI-based boot flow.
So let me summarize the discussion about PlatformInitLib.4. But a basic version of PlatformInitLib is a good start.Yes. Having initially only the functions needed by config-b in PlatformInitLib
1. PlatformInitLib wraps the common functions in OvmfPkg/PlatformPei.Yes. Everything needed for PEI-less / config-b boot moves to
PlatformInitLib is added as dependency to OvmfPkg/PlatformPei, so
PlatformPei can call those functions when booting with PEI.
PEI-less boot will add PlatformInitLib to SEC (and DXE) instead
so the same code can be used then.
Not sure how to handle cmos best. Not needed for memory detection on
qemu, but cloudhw depends on it so it is back for now. Will cloudhw
support tdx too btw?
And PlatformInitLib willAt least not initially. Maybe later when we move more code to the lib
to reduce code duplication in xen/bhyve/qemu PlatformPei variants.
2. OvmfPkg/PlatformPei will be refactored with PlatformInitLib. The
3. Config-B support PEI-less boot for both legacy guest and td guest.Yes.