From: Marvin H?user <Marvin.Haeuser@outlook.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"achin.gupta@arm.com" <achin.gupta@arm.com>,
"jiewen.yao@intel.com" <jiewen.yao@intel.com>,
"supreeth.venkatesh@arm.com" <supreeth.venkatesh@arm.com>
Subject: StandaloneMmPkg comments
Date: Fri, 20 Jul 2018 18:57:38 +0000 [thread overview]
Message-ID: <VI1PR0801MB179093A5C5BC34F78BAB101980510@VI1PR0801MB1790.eurprd08.prod.outlook.com> (raw)
Good day,
I have been reading through the recently imported StandaloneMmPkg and found three odd things.
1. GUID prefixes: GUIDs defined in StandaloneMmPkg.dec either have no common prefix at all ("gMmFv") or use the "gEfi" prefix. Maybe the MdeModulePkg-style "gEdkii" prefix could be used for a uniform style?
2. The "gEfiMmConfigurationProtocolGuid" name is common between Standalone (StandaloneMmPkg.dec) and Traditional (MdePkg.dec) MM context despite having a different value of course. Shouldn't the naming reflect which is traditional and which is Standalone? I haven't checked in depth, but which is chosen when a module consumes both MdePkg and StandaloneMmPkg?
3. While .dec already uses the "Mmram" naming scheme, its header declares the MemoryReserve GUID as "gEfiMmPeiS(!)mramMemoryReserveGuid". Furthermore, the header references the SMM CIS (which has been replaced with "MM CIS" as part of the renaming), while the GUID has changed and the structure does not match the deprecated specification anyway. May I suggest to turn this GUID into a "gEdkii"-style GUID and remove all references to the SMM CIS? Maybe use the "EDKII_" prefix for "EFI_MMRAM_HOB_DESCRIPTOR_BLOCK" too? I wanted to prepare a patch, but I cannot compile the package at the moment and don't want to risk submitting anything broken.
Thanks for your time!
Regards,
Marvin.
next reply other threads:[~2018-07-20 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 18:57 Marvin H?user [this message]
2018-07-21 15:51 ` StandaloneMmPkg comments Ard Biesheuvel
2018-07-21 22:15 ` Marvin Häuser
2018-07-23 16:56 ` Supreeth Venkatesh
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=VI1PR0801MB179093A5C5BC34F78BAB101980510@VI1PR0801MB1790.eurprd08.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