From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
Leif Lindholm <leif@nuviainc.com>,
Sami Mujawar <sami.mujawar@arm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH resend 0/7] Add support for MM communicate2 protocol (PI 1.7a)
Date: Mon, 11 May 2020 16:09:34 +0200 [thread overview]
Message-ID: <058bcfe9-7fb8-ef96-410d-1adf7a57d82e@arm.com> (raw)
In-Reply-To: <BN6PR11MB3972B06500E5059BB6D3E5DB80A10@BN6PR11MB3972.namprd11.prod.outlook.com>
On 5/11/20 4:08 PM, Gao, Liming wrote:
> Ard:
> I see this change updates VariableSmmRuntimeDxe to consume mMmCommunication2 with mVariableBufferPhysical and mVariableBuffer for physical and virtual.
> But, FaultTolerantWriteSmmDxe consumes mMmCommunication2 with the same SmmCommunicateHeader for physical and virtual.
>
> Is there any difference between them?
>
Yes. The FTW code never executes at runtime, so it is guaranteed that
physical == virtual.
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ard Biesheuvel
>> Sent: Thursday, May 7, 2020 1:27 AM
>> To: devel@edk2.groups.io
>> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
>> <liming.gao@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Wu, Hao A <hao.a.wu@intel.com>; Leif Lindholm
>> <leif@nuviainc.com>; Sami Mujawar <sami.mujawar@arm.com>; Yao, Jiewen <jiewen.yao@intel.com>
>> Subject: [edk2-devel] [PATCH resend 0/7] Add support for MM communicate2 protocol (PI 1.7a)
>>
>> Now that version 1.7 errata A of the PI spec has finally been released,
>> we can take another look at this series, which incorporates the new MM
>> communicate2 protocol definition, updates the producers for conventional
>> SMM and standalone MM, and updates the variable store components to consume
>> the new version of the protocol. This solves a long standing compatibility
>> issue which made standalone MM fundamentally incompatible with a virtually
>> remapped address space as installed by SetVirtualAddressMap().
>>
>> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>> Cc: Liming Gao <liming.gao@intel.com>
>> Cc: Jian J Wang <jian.j.wang@intel.com>
>> Cc: Hao A Wu <hao.a.wu@intel.com>
>> Cc: Leif Lindholm <leif@nuviainc.com>
>> Cc: Sami Mujawar <sami.mujawar@arm.com>
>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>>
>> Ard Biesheuvel (7):
>> MdePkg: introduce MM communicate 2 protocol
>> MdeModulePkg/SmmIpl: expose MM communicate 2 protocol
>> ArmPkg/MmCommunicationDxe: expose MM Communicate 2 protocol
>> MdeModulePkg/VariableInfo: switch to MM communicate 2 protocol
>> MdeModulePkg/FaultTolerantWriteSmmDxe: switch to MM communicate 2
>> MdeModulePkg/VariableSmmRuntimeDxe: switch to MM communicate 2
>> StandaloneMmPkg: switch to MM communicate 2 protocol
>>
>> .../MmCommunicationDxe/MmCommunication.c | 81 +++++++++----------
>> .../MmCommunicationDxe/MmCommunication.inf | 6 +-
>> .../Application/VariableInfo/VariableInfo.c | 19 +++--
>> .../Application/VariableInfo/VariableInfo.inf | 2 +-
>> MdeModulePkg/Core/PiSmmCore/PiSmmIpl.c | 80 ++++++++++++++++++
>> MdeModulePkg/Core/PiSmmCore/PiSmmIpl.inf | 1 +
>> MdeModulePkg/Include/Guid/SmmVariableCommon.h | 6 +-
>> .../FaultTolerantWriteSmmCommon.h | 2 +-
>> .../FaultTolerantWriteSmmDxe.c | 25 +++---
>> .../FaultTolerantWriteSmmDxe.h | 2 +-
>> .../FaultTolerantWriteSmmDxe.inf | 4 +-
>> .../RuntimeDxe/VariableSmmRuntimeDxe.c | 39 ++++-----
>> .../RuntimeDxe/VariableSmmRuntimeDxe.inf | 4 +-
>> MdePkg/Include/Protocol/MmCommunication2.h | 69 ++++++++++++++++
>> MdePkg/MdePkg.dec | 7 ++
>> StandaloneMmPkg/Core/StandaloneMmCore.h | 2 +-
>> .../StandaloneMmCpu/AArch64/StandaloneMmCpu.h | 2 +-
>> 17 files changed, 256 insertions(+), 95 deletions(-)
>> create mode 100644 MdePkg/Include/Protocol/MmCommunication2.h
>>
>> --
>> 2.17.1
>>
>>
>>
>
next prev parent reply other threads:[~2020-05-11 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 17:27 [PATCH resend 0/7] Add support for MM communicate2 protocol (PI 1.7a) Ard Biesheuvel
2020-05-06 17:27 ` [PATCH resend 1/7] MdePkg: introduce MM communicate 2 protocol Ard Biesheuvel
2020-05-12 17:09 ` [edk2-devel] " Sami Mujawar
2020-05-06 17:27 ` [PATCH resend 2/7] MdeModulePkg/SmmIpl: expose " Ard Biesheuvel
2020-05-12 17:09 ` [edk2-devel] " Sami Mujawar
2020-05-06 17:27 ` [PATCH resend 3/7] ArmPkg/MmCommunicationDxe: expose MM Communicate " Ard Biesheuvel
2020-05-12 9:30 ` Leif Lindholm
2020-05-12 17:21 ` [edk2-devel] " Sami Mujawar
2020-05-06 17:27 ` [PATCH resend 4/7] MdeModulePkg/VariableInfo: switch to MM communicate " Ard Biesheuvel
2020-05-06 17:53 ` [EXTERNAL] [edk2-devel] " Bret Barkelew
2020-05-12 17:10 ` Sami Mujawar
2020-05-06 17:27 ` [PATCH resend 5/7] MdeModulePkg/FaultTolerantWriteSmmDxe: switch to MM communicate 2 Ard Biesheuvel
2020-05-12 17:10 ` [edk2-devel] " Sami Mujawar
2020-05-06 17:27 ` [PATCH resend 6/7] MdeModulePkg/VariableSmmRuntimeDxe: " Ard Biesheuvel
2020-05-12 17:10 ` [edk2-devel] " Sami Mujawar
2020-05-06 17:27 ` [PATCH resend 7/7] StandaloneMmPkg: switch to MM communicate 2 protocol Ard Biesheuvel
2020-05-12 17:10 ` [edk2-devel] " Sami Mujawar
2020-05-11 14:08 ` [edk2-devel] [PATCH resend 0/7] Add support for MM communicate2 protocol (PI 1.7a) Liming Gao
2020-05-11 14:09 ` Ard Biesheuvel [this message]
2020-05-11 14:32 ` Liming Gao
2020-05-12 21:52 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=058bcfe9-7fb8-ef96-410d-1adf7a57d82e@arm.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox