public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <jiewen.yao@intel.com>,
	"'Lin, Du'" <du.lin@intel.com>
Cc: "'Ard Biesheuvel'" <ardb+tianocore@kernel.org>,
	"'Gerd Hoffmann'" <kraxel@redhat.com>
Subject: 回复: [edk2-devel] [PATCH] OvmfPkg: Update VMM Hob list check to support new resource attributes
Date: Mon, 27 May 2024 15:11:32 +0800	[thread overview]
Message-ID: <016001dab005$1a9294f0$4fb7bed0$@byosoft.com.cn> (raw)
In-Reply-To: <MW4PR11MB58726677549C0012D26546358CF02@MW4PR11MB5872.namprd11.prod.outlook.com>

Jiewen:
  If the patch is urgent to be merged, I will help add push label to merge
it with current process. 
  
  If the patch is not urgent, it can be merged after TianoCore Code Review
is switched from email to GitHub Pull Requests on US Tuesday.

Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Yao, Jiewen
> 发送时间: 2024年5月27日 14:43
> 收件人: Lin, Du <du.lin@intel.com>; devel@edk2.groups.io
> 抄送: Ard Biesheuvel <ardb+tianocore@kernel.org>; Gerd Hoffmann
> <kraxel@redhat.com>
> 主题: Re: [edk2-devel] [PATCH] OvmfPkg: Update VMM Hob list check to
support
> new resource attributes
> 
> I have approved it.
> 
> What is the process to merge? There is no COMMIT button or PUSH label.
> 
> 
> > -----Original Message-----
> > From: Lin, Du <du.lin@intel.com>
> > Sent: Monday, May 27, 2024 2:23 PM
> > To: devel@edk2.groups.io
> > Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>; Gerd Hoffmann
> > <kraxel@redhat.com>; Yao, Jiewen <jiewen.yao@intel.com>; Lin, Du
> > <du.lin@intel.com>
> > Subject: RE: [edk2-devel] [PATCH] OvmfPkg: Update VMM Hob list check to
> > support new resource attributes
> >
> > Thanks for the review and approval. Could you please help merge this
patch to
> > the upstream? A pull request has been created for this patch:
> > https://github.com/tianocore/edk2/pull/5644. Thanks.
> >
> > BRs,
> > Lin, Du
> >
> > -----Original Message-----
> > From: Yao, Jiewen <jiewen.yao@intel.com>
> > Sent: Thursday, May 16, 2024 5:37 PM
> > To: devel@edk2.groups.io; Lin, Du <du.lin@intel.com>
> > Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>; Gerd Hoffmann
> > <kraxel@redhat.com>
> > Subject: RE: [edk2-devel] [PATCH] OvmfPkg: Update VMM Hob list check to
> > support new resource attributes
> >
> > Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>
> >
> > > -----Original Message-----
> > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Lin, Du
> > > Sent: Thursday, May 9, 2024 1:27 PM
> > > To: devel@edk2.groups.io
> > > Cc: Lin, Du <du.lin@intel.com>; Ard Biesheuvel
> > > <ardb+tianocore@kernel.org>; Gerd Hoffmann <kraxel@redhat.com>; Yao,
> > > Jiewen <jiewen.yao@intel.com>
> > > Subject: [edk2-devel] [PATCH] OvmfPkg: Update VMM Hob list check to
> > > support new resource attributes
> > >
> > > Encrypted and Special Purpose resource attributes are introduced in PI
> > > 1.8 Specification. This patch is to update VMM Hob list integrity
> > > check to recognise these resource attributes.
> > >
> > > Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> > > Cc: Gerd Hoffmann <kraxel@redhat.com>
> > > Cc: Jiewen Yao <jiewen.yao@intel.com>
> > > Signed-off-by: Du Lin <du.lin@intel.com>
> > > ---
> > >  OvmfPkg/IntelTdx/TdxHelperLib/SecTdxHelper.c | 2 ++
> > >  1 file changed, 2 insertions(+)
> > >
> > > diff --git a/OvmfPkg/IntelTdx/TdxHelperLib/SecTdxHelper.c
> > > b/OvmfPkg/IntelTdx/TdxHelperLib/SecTdxHelper.c
> > > index b6085eab44..19e9b1bf54 100644
> > > --- a/OvmfPkg/IntelTdx/TdxHelperLib/SecTdxHelper.c
> > > +++ b/OvmfPkg/IntelTdx/TdxHelperLib/SecTdxHelper.c
> > > @@ -643,6 +643,8 @@ ValidateHobList (
> > >
> > > EFI_RESOURCE_ATTRIBUTE_PERSISTABLE |
> > >
> > > EFI_RESOURCE_ATTRIBUTE_READ_ONLY_PROTECTED |
> > >
> > > EFI_RESOURCE_ATTRIBUTE_READ_ONLY_PROTECTABLE |
> > > +
> > > + EFI_RESOURCE_ATTRIBUTE_ENCRYPTED|
> > > +
> > > EFI_RESOURCE_ATTRIBUTE_SPECIAL_PURPOSE |
> > >
> > > EFI_RESOURCE_ATTRIBUTE_MORE_RELIABLE))) != 0)
> > >          {
> > >            DEBUG ((DEBUG_ERROR, "HOB: Unknow ResourceDescriptor
> > > ResourceAttribute type. Type: 0x%08x\n", Hob.ResourceDescriptor-
> > > >ResourceAttribute));
> > > --
> > > 2.44.0.windows.1
> > >
> > >
> > >
> > >
> > >
> 
> 
> 
> 
> 





-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119277): https://edk2.groups.io/g/devel/message/119277
Mute This Topic: https://groups.io/mt/106326539/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-05-27  7:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17CDBAD36E570CF2.8965@groups.io>
2024-05-16  9:37 ` [edk2-devel] [PATCH] OvmfPkg: Update VMM Hob list check to support new resource attributes Yao, Jiewen
2024-05-17  5:36   ` Du Lin
2024-05-27  6:22   ` Du Lin
2024-05-27  6:42     ` Yao, Jiewen
2024-05-27  7:11       ` gaoliming via groups.io [this message]
2024-05-27  7:12         ` Yao, Jiewen
     [not found]         ` <17D347097EAE4902.28935@groups.io>
2024-05-29 23:59           ` Yao, Jiewen
2024-05-30 10:26             ` Du Lin
2024-05-30 10:30               ` Yao, Jiewen
2024-05-30 12:06                 ` Du Lin
2024-05-30 12:11                   ` Yao, Jiewen

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='016001dab005$1a9294f0$4fb7bed0$@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