From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Xu, Min M" <min.m.xu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Aktas, Erdem" <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg: Store PageTablePool in TdxWorkArea
Date: Fri, 23 Sep 2022 07:43:34 +0200 [thread overview]
Message-ID: <20220923054334.lra4csta2haobx7y@sirius.home.kraxel.org> (raw)
In-Reply-To: <PH0PR11MB5064C8FBDB99346C7429A5B7C54E9@PH0PR11MB5064.namprd11.prod.outlook.com>
On Thu, Sep 22, 2022 at 04:43:04AM +0000, Xu, Min M wrote:
> Hi, Gerd
> Do you have any comments on this patch?
Looks ok to me.
But I'm increasingly wondering whenever it actually was that a smart
move to ditch the PEI phase for the IntelTdx builds. Anything which
can't be handled in DXE must be done in SEC, and the SEC restrictions
seem to be a constant struggle.
We had that when adding tdx measurement support which required sha*
hash support for SEC. And this looks like another case ...
take care,
Gerd
next prev parent reply other threads:[~2022-09-23 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1712727D109677C5.26635@groups.io>
2022-09-22 4:43 ` [edk2-devel] [PATCH 1/1] OvmfPkg: Store PageTablePool in TdxWorkArea Min Xu
2022-09-23 5:43 ` Gerd Hoffmann [this message]
2022-09-27 3:00 ` Yao, Jiewen
2022-09-27 3:02 ` 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=20220923054334.lra4csta2haobx7y@sirius.home.kraxel.org \
--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