From: "Cohen, Eugene" <eugene@hp.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Achin Gupta <Achin.Gupta@arm.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>, nd <nd@arm.com>,
Laszlo Ersek <lersek@redhat.com>,
"Zhang, Chao B" <chao.b.zhang@intel.com>
Subject: Re: [PATCH v2 04/11] MdePkg/Include: Add StandaloneMmServicesTableLib library
Date: Sun, 13 Jan 2019 12:42:00 +0000 [thread overview]
Message-ID: <TU4PR8401MB12007751E55547E200D5E26EB4870@TU4PR8401MB1200.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAKv+Gu82pDKrm6_eonTcqarEOXueQsCQydx3sGDmNni69qj4ig@mail.gmail.com>
I saw this thread earlier this week and wanted to chime in.
> > Also, there are some other pieces missing (which I mentioned in one of
> > the other threads but I suppose you may not have caught up yet):
> > EndOfDxe (as well as some other PI defined events) needs to be
> > signalled to the standalone MM context by some non-MM agent, and I
> > think there are other parts of the traditional SMM IPL that have not
> > been ported to standalone MM yet.
I haven't been following closely the state of StandaloneMmPkg on edk2 - as we were ready to sync up some of our earlier MM stuff to edk2 I learned that the support in place is only partial as patches have been coming in slowly so we chose to implement a version based on the early joint prototype work we did ("uefiproto" repo). In this there is a DXE component that produces the SMM Communication protocol and also ensures that when key GUIDed events occur in DXE that they are forwarded to MM including EndOfDxe.
I don't see a strong argument for not forwarding the event signaling information to MM - MM can either use the information or ignore it as it sees fit. I can see scenarios around variable services where knowing what phase of boot the normal world is in is necessary.
Eugene
next prev parent reply other threads:[~2019-01-13 12:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 13:13 [PATCH v2 00/11] Extend secure variable service to be usable from Standalone MM Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 01/11] StandaloneMmPkg: Remove MM_STANDALONE LIBRARY_CLASS from StandaloneMmCoreHobLib Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 02/11] StandaloneMmPkg: Adding the library packages used by MM_STANDALONE drivers Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 03/11] MdeModulePkg: Add a PCD to indicate Standalone MM supports secure variable Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 04/11] MdePkg/Include: Add StandaloneMmServicesTableLib library Jagadeesh Ujja
2019-01-03 11:03 ` Ard Biesheuvel
2019-01-03 16:14 ` Laszlo Ersek
2019-01-04 11:57 ` Ard Biesheuvel
2019-01-07 15:28 ` Laszlo Ersek
2019-01-07 17:33 ` Ard Biesheuvel
2019-01-07 18:50 ` Achin Gupta
2019-01-07 18:55 ` Ard Biesheuvel
2019-01-07 19:21 ` Achin Gupta
2019-01-07 19:37 ` Ard Biesheuvel
2019-01-08 1:11 ` Laszlo Ersek
2019-01-08 13:27 ` Ard Biesheuvel
2019-01-08 16:52 ` Laszlo Ersek
2019-01-13 12:42 ` Cohen, Eugene [this message]
2019-01-14 18:51 ` Ard Biesheuvel
2019-01-02 13:13 ` [PATCH v2 05/11] MdeModulePkg/FaultTolerantWriteDxe: allow reusability as a MM driver Jagadeesh Ujja
2019-01-02 17:15 ` Ard Biesheuvel
2019-01-02 13:13 ` [PATCH v2 06/11] MdeModulePkg/Variable/RuntimeDxe: adapt for usability with MM Standalone Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 07/11] MdeModulePkg/Variable/RuntimeDxe: adapt as a MM Standalone driver Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 08/11] MdeModulePkg/VarCheckLib: allow MM_STANDALONE drivers to use this library Jagadeesh Ujja
2019-01-04 10:36 ` Ard Biesheuvel
2019-01-02 13:13 ` [PATCH v2 09/11] ArmPlatformPkg/NorFlashDxe: allow reusability as a MM driver Jagadeesh Ujja
2019-01-02 13:13 ` [PATCH v2 10/11] SecurityPkg/AuthVariableLib: allow MM_STANDALONE drivers to use this library Jagadeesh Ujja
2019-01-03 1:14 ` Zhang, Chao B
2019-01-03 6:15 ` Jagadeesh Ujja
2019-01-04 10:41 ` Ard Biesheuvel
2019-01-02 13:13 ` [PATCH v2 11/11] CryptoPkg/BaseCryptLib: " Jagadeesh Ujja
2019-01-04 10:35 ` 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=TU4PR8401MB12007751E55547E200D5E26EB4870@TU4PR8401MB1200.NAMPRD84.PROD.OUTLOOK.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