On Tue, 5 Mar 2019 at 14:32, Ard Biesheuvel <ard.biesheu...@linaro.org> wrote:
>
> This series is a further cleanup of the StandaloneMmPkg infrastructure
> used to implement UEFI secure boot on ARM systems.
>
> The first 5 patches are simple cleanups.
>
> Patch #6 adds support for dispatching a compressed firmware volume in the
> standalone MM context, so that all drivers except the core can be delivered
> in an encapsulated compressed FV, which saves quite some space.
>
> Patch #7 modifies the driver dispatch logic in the MM context so that the
> dispatcher continues until all drivers are dispatched, rather than waiting
> for a nudge from the non-secure side once the CPU driver has been loaded.
>
> Patch #8 removes support for the FV dispatch MM call.
>
> Patch #9 removes support for legacy boot handling.
>
> Patch #10 implements relaying architected PI events from DXE into MM by
> the MM communicate driver.
>
> Cc: Achin Gupta <achin.gu...@arm.com>
> Cc: Supreeth Venkatesh <supreeth.venkat...@arm.com>
> Cc: Jiewen Yao <jiewen....@intel.com>
> Cc: Leif Lindholm <leif.lindh...@linaro.org>
> Cc: Jagadeesh Ujja <jagadeesh.u...@arm.com>
>
> Ard Biesheuvel (10):
>   StandaloneMmPkg: drop redundant definition of
>     gEfiMmConfigurationProtocolGuid
>   StandaloneMmPkg: switch to NULL DebugLib resolution
>   StandaloneMmPkg/StandaloneMmCoreEntryPoint: drop explicit
>     SerialPortLib call
>   StandaloneMmPkg/Core: permit encapsulated firmware volumes
>   StandaloneMmPkg/Core: dispatch all drivers at init time
>   StandaloneMmPkg/Core: drop support for dispatching FVs into MM
>   StandaloneMmPkg/Core: remove legacy boot support

Pushed the 7 patches above as 326598e9b759..b2877855c7ec.

>   StandaloneMmPkg: drop unused PCD PcdStandaloneMmEnable
>   StandaloneMmPkg: remove redundant StandaloneMmDriverEntryPoint driver

These 2 are ready to go, but are dependent on edk2-platforms patches
that are under review.

>   ArmPkg/MmCommunicationDxe: signal architected PI events into MM
>     context

This one is still under discussion, since we need to clarify which
events need to be signaled into the MM context.
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to