Add DXE, SMM, and STANDALONE MM implementations of the=0D MemoryProtectionHobLib.=0D =0D Signed-off-by: Taylor Beebe <t@...>=0D Cc: Jian J Wang <jian.j.wang@...>=0D Cc: Liming Gao <gaoliming@...>=0D C

DxeMemoryProtectionHobLib and MmMemoryProtectionHobLib will fetch=0D the memory protection settings HOB entry for their respective phase,=0D validate the settings, and populate a global for access.=0D

These headers provide settings definitions for memory protections,=0D settings profiles for easily enabling memory protections,=0D and the GUIDs used for producing the memory protection HOB.=0D =0D Th

Memory protection settings are currently configured via FixedAtBuild PCDs which resulted in a build-time configuration of memory mitigations. To improve flexibility and compatibility, this patchset ad

From 4282ca25cde475a4ec2b81c5e878414a5829f88b Mon Sep 17 00:00:00 2001 Message-Id: <4282ca25cde475a4ec2b81c5e878414a5829f88b.1684880087.git.nolan.hergert@...> In-Reply-To: <cover.1684880087.git.nolan.

Reviewed-by: Ashraf Ali S <ashraf.ali.s@...>

From: Ranbir Singh <Ranbir.Singh3@...> The return value stored in Status after call to SetDriveParameters is not made of any use thereafter and hence it remains as UNUSED. Add error check as is done a

From: Ranbir Singh <Ranbir.Singh3@...> Line number 1348 does contain a typecast with UINT32, but it is after all the operations (16-bit left shift followed by OR'ing) are over. To avoid any SIGN_EXTEN

v1 -> v2: - Retain outer cast - Add error check instead of Status storage removal Ranbir Singh (2): MdeModulePkg/Bus/Ata/AtaAtapiPassThru: Fix SIGN_EXTENSION Coverity issue MdeModulePkg/Bus/Ata/AtaAta

# Agenda: **Presentation Topics:** No topics **Opens:** Paul Luse (Intel)- Volunteering to help with OpenSSL 3.0 migration Rebecca Cran – Looking long term moving away from make Brian Johnson – Attemp

Because SMM perf-logging is migrated to non-SMRAM at ReadyToBoot by DxeCorePerformanceLib, the perf-logging after ExitBS is useless and impact the SMI latency at runtime. Hence the SmmCorePerformanceL

Because SMM perf-logging is migrated to non-SMRAM at ReadyToBoot by DxeCorePerformanceLib, the perf-logging after ExitBS is useless and impact the SMI latency at runtime. Hence the SmmPerformanceLib i

SmmDriverDispatchHandler is the routine that dispatches SMM drivers from FV. It's a time-consuming routine. Add perf-logging for this routine. Signed-off-by: Ray Ni <ray.ni@...> Cc: Jian J Wang <jian.

Following procedures are perf-logged: * SmmReadyToBootHandler * SmmReadyToLockHandler * SmmEndOfDxeHandler * SmmEntryPoint (It's the main routine run in BSP when SMI happens.) * SmiManage Cc: Jian J W

MP procedures are those procedures that run in every CPU thread. The EDKII perf infra is not MP safe so it doesn't support to be called from those MP procedures. The patch adds SMM MP perf-logging sup

The patch adds perf-logging for the following potential time-consuming BSP procedures: * PiCpuSmmEntry - SmmRelocateBases * ExecuteFirstSmiInit * BSPHandler - SmmWaitForApArrival - PerformRemainingTas

In UnsetGuardPage(), before SmmReadyToLock, remove NX and RO memory attribute protection for guarded page since EfiConventionalMemory in SMRAM is RW and executable before SmmReadyToLock. If UnsetGuard

Remove code that apply AddressEncMask to non-leaf entry when split smm page table by MemEncryptSevLib. In FvbServicesSmm driver, it calls MemEncryptSevClearMmioPageEncMask to clear AddressEncMask bit

In the V6 patch set: In 'MdeModulePkg: Remove other attribute protection in UnsetGuardPage', add code to apply EFI_MEMORY_XP to the guarded page to be freed in UnsetGuardPage() if it happens after Smm

Remove RO and NX protection when unset guard page. When UnsetGuardPage(), remove all the memory attribute protection for guarded page. Signed-off-by: Dun Tan <dun.tan@...> Cc: Liming Gao <gaoliming@..