From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <min.m.xu@intel.com>
Cc: "'Kinney, Michael D'" <michael.d.kinney@intel.com>,
"'Liu, Zhiguang'" <zhiguang.liu@intel.com>,
"'Yao, Jiewen'" <jiewen.yao@intel.com>,
"'Wang, Jian J'" <jian.j.wang@intel.com>,
"'Lu, Ken'" <ken.lu@intel.com>,
"'Sami Mujawar'" <sami.mujawar@arm.com>,
"'Gerd Hoffmann'" <kraxel@redhat.com>
Subject: 回复: [edk2-devel] 回复: [PATCH V4 1/3] MdePkg: Introduce CcMeasurementProtocol for CC Guest firmware
Date: Fri, 5 Nov 2021 13:20:03 +0800 [thread overview]
Message-ID: <000901d7d204$c9b25a10$5d170e30$@byosoft.com.cn> (raw)
In-Reply-To: <CO1PR11MB5058AC1C3AA6A6202E0B5DC0C58D9@CO1PR11MB5058.namprd11.prod.outlook.com>
Min:
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Min Xu
> 发送时间: 2021年11月4日 20:35
> 收件人: devel@edk2.groups.io; gaoliming@byosoft.com.cn
> 抄送: Kinney, Michael D <michael.d.kinney@intel.com>; Liu, Zhiguang
> <zhiguang.liu@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Wang, Jian J
> <jian.j.wang@intel.com>; Lu, Ken <ken.lu@intel.com>; 'Sami Mujawar'
> <sami.mujawar@arm.com>; 'Gerd Hoffmann' <kraxel@redhat.com>
> 主题: Re: [edk2-devel] 回复: [PATCH V4 1/3] MdePkg: Introduce
> CcMeasurementProtocol for CC Guest firmware
>
> On November 4, 2021 1:51 PM, Gao, Liming wrote:
> > Min:
> > I have one minor comment. gEfiCcFinalEventsTableGuid may be placed
> into
> > [Guids] section instead of [Protocols] section.
> >
> Hi, Liming
> I follow the definition of gEfiTcg2ProtocolGuid and
> gEfiTcg2FinalEventsTableGuid. See
> https://github.com/tianocore/edk2/blob/master/MdePkg/MdePkg.dec#L159
> 0-L1592
> Actually gEfiCcMeasurementProtocolGuid and gEfiCcFinalEventsTableGuid are
> the counterpart protocol/guid definition in Confidential Computing measure
> boot.
> I am not sure if there is some other consideration that
gEfiTcg2ProtocolGuid
> and gEfiTcg2FinalEventsTableGuid are defined in the section of
[Protocols].
I find gEfiTcg2FinalEventsTableGuid is used for configuration table. This is
one Guid usage.
It should be placed into [Guids] section.
You can see hash protocol and hash algorithm guid in MdePkg.
gEfiHashProtocolGuid is defined in [Protocols] section, and
gEfiHashAlgorithmMD5Guid
is defined in [Guids] section. They are both from
MdePkg/Include/Protocol/Hash.h.
So, I suggest to follow the guid usage to define this Guid into the
different section.
Thanks
Liming
>
> Thanks
> Min
>
>
>
>
next prev parent reply other threads:[~2021-11-05 5:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 2:50 [PATCH V4 0/3] Introduce CcMeasurementProtocol into EDK2 Min Xu
2021-11-02 2:50 ` [PATCH V4 1/3] MdePkg: Introduce CcMeasurementProtocol for CC Guest firmware Min Xu
2021-11-02 6:24 ` Yao, Jiewen
2021-11-02 9:41 ` Sami Mujawar
2021-11-04 5:51 ` 回复: " gaoliming
2021-11-04 12:35 ` [edk2-devel] " Min Xu
2021-11-05 5:20 ` gaoliming [this message]
2021-11-05 6:22 ` Min Xu
2021-11-02 2:50 ` [PATCH V4 2/3] SecurityPkg: Support CcMeasurementProtocol in DxeTpm2MeasureBootLib Min Xu
2021-11-02 6:24 ` Yao, Jiewen
2021-11-03 2:59 ` Min Xu
2021-11-02 9:43 ` Sami Mujawar
2021-11-05 2:12 ` [edk2-devel] " Min Xu
2021-11-02 2:50 ` [PATCH V4 3/3] SecurityPkg: Support CcMeasurementProtocol in DxeTpmMeasurementLib Min Xu
2021-11-02 6:24 ` Yao, Jiewen
2021-11-03 3:01 ` Min Xu
2021-11-02 9:45 ` Sami Mujawar
2021-11-04 8:20 ` Gerd Hoffmann
2021-11-04 13:35 ` [edk2-devel] " Min Xu
2021-11-04 13:49 ` Min Xu
2021-11-04 14:18 ` Sami Mujawar
2021-11-04 14:25 ` Yao, Jiewen
2021-11-05 2:15 ` Min Xu
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='000901d7d204$c9b25a10$5d170e30$@byosoft.com.cn' \
--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