From: "Min Xu" <min.m.xu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>
Cc: "Aktas, Erdem" <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH V2 3/4] OvmfPkg/IoMmuDxe: Add SEV support for reserved shared memory
Date: Tue, 13 Dec 2022 23:55:50 +0000 [thread overview]
Message-ID: <SJ0PR11MB506955ACC14748766453B229C5E39@SJ0PR11MB5069.namprd11.prod.outlook.com> (raw)
In-Reply-To: <44b6e3ca-69e4-bc23-6a46-6138456c7ae1@amd.com>
On December 14, 2022 12:05 AM, Lendacky, Thomas wrote:
> On 12/12/22 23:48, Min Xu wrote:
> > From: Tom Lendacky <thomas.lendacky@amd.com>
> >
> > Add support to use the reserved shared memory within the IoMmu library.
> > This improves boot times for all SEV guests, with SEV-SNP benefiting
> > the most as it avoids the page state change call to the hypervisor.
>
> Thanks for including the patch, Min.
>
> One difference between my original and yours noted below, feel free to
> ignore, though.
>
> Otherwise, tested and validated.
>
> >
> > - if (CC_GUEST_IS_SEV (PcdGet64 (PcdConfidentialComputingGuestAttr)))
> {
> > - //
> > - // Clear the memory encryption mask on the plaintext buffer.
> > - //
> > - Status = MemEncryptSevClearPageEncMask (
> > - 0,
> > - MapInfo->PlainTextAddress,
> > - MapInfo->NumberOfPages
> > - );
> > - } else if (CC_GUEST_IS_TDX (PcdGet64
> > (PcdConfidentialComputingGuestAttr))) {
> > + if (MapInfo->ReservedMemBitmap == 0) {
> > //
> > // Set the memory shared bit.
>
> My original patch deleted this line since it is different for each type of CC
> guest and commented about in each if block.
>
Thanks for reminder. I will delete this line in the next version.
Thanks
Min
next prev parent reply other threads:[~2022-12-13 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 5:48 [PATCH V2 0/4] Reserve shared memory for DMA operation Min Xu
2022-12-13 5:48 ` [PATCH V2 1/4] OvmfPkg/IoMmuDxe: Reserve shared memory region " Min Xu
2022-12-13 16:04 ` Lendacky, Thomas
2022-12-14 0:02 ` [edk2-devel] " Min Xu
2022-12-14 14:24 ` Lendacky, Thomas
2022-12-13 5:48 ` [PATCH V2 2/4] OvmfPkg/IoMmuDxe: Rename AmdSevIoMmu to CcIoMmu Min Xu
2022-12-13 5:48 ` [PATCH V2 3/4] OvmfPkg/IoMmuDxe: Add SEV support for reserved shared memory Min Xu
2022-12-13 16:05 ` Lendacky, Thomas
2022-12-13 23:55 ` Min Xu [this message]
2022-12-13 5:48 ` [PATCH V2 4/4] Maintainers: Update OvmfPkg/IoMmuDxe Min Xu
[not found] ` <1730444AD2D72EE9.23954@groups.io>
2022-12-13 5:52 ` [edk2-devel] [PATCH V2 3/4] OvmfPkg/IoMmuDxe: Add SEV support for reserved shared memory Min Xu
2022-12-13 15:35 ` Lendacky, Thomas
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=SJ0PR11MB506955ACC14748766453B229C5E39@SJ0PR11MB5069.namprd11.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