These changes update references to the MessageLength field of
EFI_MM_COMMUNICATE_HEADER to use consistent integer width.
This structure can be used for both PEI and DXE MM communication.
Thus, for a system that supports PEI MM launch with a 32-bit PEI
environment and a 64-bit MM environment, the current
EFI_MM_COMMUNICATE_HEADER definition will cause structure parse
error due to the use of UINTN.
[x] Breaking change?
[ ] Impacts security?
[ ] Includes tests?
Marked as breaking due to a change in the definition of EFI_MM_COMMUNICATE_HEADER.
How This Was Tested
CI
Verify MM communication with 32-bit PEI and 64-bit MM
Integration Instructions
Review any potential usage of EFI_MM_COMMUNICATE_HEADER to compensate
for the MessageLength field being a UINT64 instead of UINTN.
Description
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3398 REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430
These changes update references to the
MessageLengthfield ofEFI_MM_COMMUNICATE_HEADERto use consistent integer width.This structure can be used for both PEI and DXE MM communication.
Thus, for a system that supports PEI MM launch with a 32-bit PEI environment and a 64-bit MM environment, the current
EFI_MM_COMMUNICATE_HEADERdefinition will cause structure parse error due to the use ofUINTN.How This Was Tested
Integration Instructions
EFI_MM_COMMUNICATE_HEADERto compensate for theMessageLengthfield being aUINT64instead ofUINTN.