REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3398 REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 MM communicate protocols are expanded with EFI_MM_COMMUNICATE_HEADER_V3 structure that

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3398 REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 This change introduces a new definition for MM communicate PPI v3. This PPI will be in

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3398 REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 This change introduces a new definition for MM communicate protocol v3. This protocol

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3398 REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 This change introduces a new definition for MM communicate header structure, intending

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 This change includes specification update markdown file that describes the proposed PI Specification v1.7 Errata A in detail and potential impa

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 This patch series is a follow up of previous submission: https://edk2.groups.io/g/devel/message/77017 Since the submission of previous patch se

Hi Dandan, Thanks for letting me know. I added Bret and Sean to the thread for broader view in our scope. But currently our StandaloneMm Core does not report performance data to FirmwarePerformanceSta

Thanks for the clarification. I will work on v-next with flexible array as Data field. Regards, Kun

Hi Mike, Thanks for the note. I will add this check for sanity check in v-next, assuming this will not fail for currently supported compilers. Just curious, what do we normally do if this type of chec

Hi Mike, Thanks for the information. I can update the patch and proposed spec change to use flexible array in v-next if there is no other concerns. After switching to flexible array, OFFSET_OF (Data)

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3440 MM Configuration PPI was defined in PI Specification since v1.5. This change added definition of such PPI and related GUIDs into MdePkg. Cc: Mi

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3440 The definition of EFI_MM_RESERVED_MMRAM_REGION, according to PI Spec 1.5 is also referenced in EFI_PEI_MM_CONFIGURATION_PPI. Defining this stru

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3440 This patch series is a follow up of previous submission: https://edk2.groups.io/g/devel/message/76748 v2 patches mainly focus on feedback for c

Hi Liming, Thanks for pointing it out. I will updated the patches shortly. Regards, Kun

Hi Hao, We have been circulating different ideas internally about how to enforce a warning around this change. There is an idea of deprecating the old structure and replacing it with a newly defined E

I can place this file under "CodeFirst" folder on the next round of patch series. It would be helpful to update the code-first process page so that others can be consistent on the process next time. T

Hi Marvin, I would prefer not to rely on undefined behaviors from different compilers. Instead of using flexible arrays, is it better to remove the `Data` field, pack the structure and follow "VARIABL

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3440 MM Configuration PPI was defined in PI Specification since v1.5. This change added definition of such PPI and related GUIDs into MdePkg. Cc: Mi

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3440 The definition of EFI_MM_RESERVED_MMRAM_REGION, according to PI Spec 1.5 is also referenced in EFI_PEI_MM_CONFIGURATION_PPI. Defining this stru

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3440 EFI_PEI_MM_CONFIGURATION_PPI is defined since PI spec v1.5. This patch series added the interface definition and related GUIDs into MdePkg. On