Dear all,
For current PiSmmCore and PiSmmIpl design, mInLegacyBoot will be set once the
LegacyBoot event been triggered.
//
// Flag to determine if the platform has performed a legacy boot.
// If this flag is TRUE, then the runtime code and runtime data associated with
the
// SMM IPL are converted to free memory, so the SMM COre must guarantee that is
// does not touch of the code/data associated with the SMM IPL if this flag is
TRUE.
//
BOOLEAN mInLegacyBoot = FALSE;
This flag been set and it make sense to not trust gSmmCorePrivate anymore IF
legacy OS booted and use the "free" memory.
But, how if the case legacy boot been tried but failed and system would like to
try next BootOption that depends on SMMCommunication?
In order to support such possible Legacy->UEFI interlaced boot requirement and
considering the case system does not successfully boot into legacy OS but would
like to try next available boot option, it will be better have a corresponding
service that can toggle mInLegacyBoot when LegacyBoot failed and SmmCommunicate
is mandatory for next boot intent.
Comment?
Regards,
-Mars
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
