Feature: AARCH64 Single Copy#264
Draft
Flickdm wants to merge 3 commits into
Draft
Conversation
mu-automation
Bot
added
language:python
Flickdm
force-pushed
the
feat/onecrypto-aarch64-single-copy
branch
from
4bf33a1 to
443a920
Compare
Add a DXE loader path that fetches OneCrypto PE bytes from StandaloneMM over EFI_MM_COMMUNICATION2_PROTOCOL, and add a StandaloneMM image provider handler that serves chunked image responses. Wire the new GUID, INF files, and DSC mappings for AARCH64 builds. Signed-off-by: Doug Flick <dougflick@microsoft.com>
Package OneCryptoLoaderDxeFromMm as OneCryptoLoaderDxe in the AARCH64 layout and include OneCryptoImageProviderStandaloneMm artifacts for the MM fetch path. Signed-off-by: Doug Flick <dougflick@microsoft.com>
Document the legacy dual-bin and single-copy AARCH64 modes, including the MM image-provider + DXE-from-MM loader path and rationale for module separation. Clarify that the single-copy mode originated from the initial platform prototype while targeting mainline integration for real AARCH64 platforms. Signed-off-by: Doug Flick <dougflick@microsoft.com>
Flickdm
force-pushed
the
feat/onecrypto-aarch64-single-copy
branch
from
98f6e5b to
9997144
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces support for a new "single-copy" AARCH64 integration mode for OneCryptoPkg, enabling DXE to fetch the OneCrypto binary from StandaloneMM via MM communication rather than requiring a separate DXE binary. The documentation is extensively updated to describe both the legacy dual-bin and the new single-copy architectures. The implementation includes a new MM module, message protocol, and GUID to support this communication path.
AARCH64 single-copy mode support
OneCryptoImageProviderStandaloneMm, which registers an MM communication handler to serve OneCrypto PE32 image bytes to DXE usingEFI_MM_COMMUNICATION2_PROTOCOL. (OneCryptoPkg/OneCryptoLoaders/OneCryptoImageProviderStandaloneMm.inf[1] [2]OneCryptoPkg/OneCryptoLoaders/OneCryptoImageProviderMm.c[3])gOneCryptoImageProviderGuid). (OneCryptoPkg/Include/Guid/OneCryptoImageProviderGuid.h)OneCryptoPkg/Include/Private/OneCryptoImageProviderMessage.h)Documentation updates
Architecture.mdto clarify the differences between X64 and AARCH64, document both legacy dual-bin and single-copy AARCH64 modes, and describe the new image provider flow and its rationale. (OneCryptoPkg/Docs/Architecture.md[1] [2] [3])FAQs.mdto explain the new single-copy AARCH64 mode, loader variants, and integration details. (OneCryptoPkg/Docs/FAQs.md[1] [2] [3] [4])OneCryptoPkg/Docs/README.md)For details on how to complete these options and their meaning refer to CONTRIBUTING.md.
How This Was Tested
<Describe the test(s) that were run to verify the changes.>
Integration Instructions
<Describe how these changes should be integrated. Use N/A if nothing is required.>