diff options
| author | Star Zeng <star.zeng@intel.com> | 2015-06-18 09:26:41 +0000 |
|---|---|---|
| committer | lzeng14 <lzeng14@Edk2> | 2015-06-18 09:26:41 +0000 |
| commit | 53ec4d7f98a6af8b00c891c3f13791967e52b6a3 (patch) | |
| tree | fd2b0b4d2b8949f0bd39cd05c46be7501b073bdd /MdePkg | |
| parent | 93e8630a8debe1bd76c175370acf684bda69d558 (diff) | |
| download | edk2-platforms-53ec4d7f98a6af8b00c891c3f13791967e52b6a3.tar.xz | |
MdeModulePkg PiSmmCore: Introduce SMM Exit Boot Services and Legacy Boot.
And also SMM Ready To Boot.
The SMM Exit Boot Service protocol is to be published by the SMM
Foundation code to associate with EFI_EVENT_GROUP_EXIT_BOOT_SERVICES
to notify SMM driver that system enter exit boot services.
The SMM Legacy Boot protocol is to be published by the SMM
Foundation code to associate with EFI_EVENT_LEGACY_BOOT_GUID
to notify SMM driver that system enter legacy boot.
The SMM Ready To Boot protocol is to be published by the SMM
Foundation code to associate with EFI_EVENT_GROUP_READY_TO_BOOT
to notify SMM driver that system enter ready to boot.
After them, any SMM drivers can get protocol notify on what happened
in DXE phase, then there is no need to let each individual SMM driver
to register SMM Communication Handler for that.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Star Zeng <star.zeng@intel.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17657 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'MdePkg')
0 files changed, 0 insertions, 0 deletions