diff options
author | Star Zeng <star.zeng@intel.com> | 2018-02-11 11:00:44 +0800 |
---|---|---|
committer | Star Zeng <star.zeng@intel.com> | 2018-03-08 21:33:50 +0800 |
commit | 112e584ba0619695b7da3bb87604b3385ac2cb6d (patch) | |
tree | 47de64109184af94e79e1e242f8e67a636fc8ec4 /IntelFrameworkPkg/Library | |
parent | d62cb7bb0c27f62373a9fb03680339f80c8fe1b3 (diff) | |
download | edk2-112e584ba0619695b7da3bb87604b3385ac2cb6d.tar.gz edk2-112e584ba0619695b7da3bb87604b3385ac2cb6d.tar.bz2 edk2-112e584ba0619695b7da3bb87604b3385ac2cb6d.zip |
SecurityPkg OpalPassword: Add solution without SMM device code
After IOMMU is enabled in S3, original solution with SMM device
code (OpalPasswordSmm) to unlock OPAL device for S3 will not work
as the DMA operation will be aborted without granted DMA buffer.
Instead, this solution is to add OpalPasswordPei to eliminate
SMM device code, and OPAL setup UI produced by OpalPasswordDxe
will be updated to send requests (set password, update password,
and etc), and then the requests will be processed in next boot
before SmmReadyToLock, password and device info will be saved to
lock box used by OpalPasswordPei to unlock OPAL device for S3.
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Chao Zhang <chao.b.zhang@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng <star.zeng@intel.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
Diffstat (limited to 'IntelFrameworkPkg/Library')
0 files changed, 0 insertions, 0 deletions