From: "duntan" <dun.tan@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Gerd Hoffmann" <kraxel@redhat.com>, "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [Patch V7 01/14] OvmfPkg:Remove code that apply AddressEncMask to non-leaf entry
Date: Thu, 29 Jun 2023 10:09:31 +0000 [thread overview]
Message-ID: <BN9PR11MB5483A573CFA38E5087824639E525A@BN9PR11MB5483.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20db2795-b5b5-1da1-d4ca-67ec0d8dc037@amd.com>
Tom,
Thanks for the comments. In V8 patch, I've refined the commit message and added comments in the code around the areas being changed to explain this code change.
Thanks,
Dun
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Lendacky, Thomas via groups.io
Sent: Tuesday, June 27, 2023 9:13 PM
To: Tan, Dun <dun.tan@intel.com>; devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>; Yao, Jiewen <jiewen.yao@intel.com>; Justen, Jordan L <jordan.l.justen@intel.com>; Gerd Hoffmann <kraxel@redhat.com>; Ni, Ray <ray.ni@intel.com>
Subject: Re: [edk2-devel] [Patch V7 01/14] OvmfPkg:Remove code that apply AddressEncMask to non-leaf entry
On 6/27/23 00:23, Dun Tan wrote:
> Remove code that apply AddressEncMask to non-leaf entry when split
s/apply/applies the/
s/entry/entries/
s/split/splitting/
> smm page table by MemEncryptSevLib. In FvbServicesSmm driver, it
s/smm page table by/SMM page table entries in/ s/In FvbServicesSmm driver, it/The FvbServicesSmm driver/
> calls MemEncryptSevClearMmioPageEncMask to clear AddressEncMask
s/clear/clear the/
> bit in page table for a specific range. In AMD SEV feature, this
> AddressEncMask bit in page table is used to indicate if the memory is
> guest private memory or shared memory. But all memory used by page
> table are treated as encrypted regardless of encryption bit.
But all memory accessed by the hardware page table walker is treated as encrypted, regardless of whether the encryption bit is present.
> So remove the EncMask bit for smm non-leaf page table entry doesn't
> impact AMD SEV feature.
> If page split happens in the AddressEncMask bit clear process, there
> will be some new non-leaf entries with AddressEncMask applied in smm
> page table. When ReadyToLock, code in PiSmmCpuDxe module will use
> CpuPageTableLib to modify smm page table. So remove code to apply
> AddressEncMask for new non-leaf entries since CpuPageTableLib doesn't
> consume the EncMask PCD.
This last paragraph is a bit confusing to read, please rewrite it so it is easier to understand.
>
> Signed-off-by: Dun Tan <dun.tan@intel.com>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Reviewed-by: Ray Ni <ray.ni@intel.com>
I think it would be best to include comments in the code around the areas being changed explaining why the the encryption mask is not being set for non-leaf entries because of the way CpuPageTableLib works.
With comments added:
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> OvmfPkg/Library/BaseMemEncryptSevLib/X64/PeiDxeVirtualMemory.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
> a/OvmfPkg/Library/BaseMemEncryptSevLib/X64/PeiDxeVirtualMemory.c
> b/OvmfPkg/Library/BaseMemEncryptSevLib/X64/PeiDxeVirtualMemory.c
> index cf2441b551..372fc03fde 100644
> --- a/OvmfPkg/Library/BaseMemEncryptSevLib/X64/PeiDxeVirtualMemory.c
> +++ b/OvmfPkg/Library/BaseMemEncryptSevLib/X64/PeiDxeVirtualMemory.c
> @@ -233,7 +233,7 @@ Split2MPageTo4K (
> // Fill in 2M page entry.
> //
> *PageEntry2M = ((UINT64)(UINTN)PageTableEntry1 |
> - IA32_PG_P | IA32_PG_RW | AddressEncMask);
> + IA32_PG_P | IA32_PG_RW);
> }
>
> /**
> @@ -352,7 +352,7 @@ SetPageTablePoolReadOnly (
> PhysicalAddress += LevelSize[Level - 1];
> }
>
> - PageTable[Index] = (UINT64)(UINTN)NewPageTable | AddressEncMask |
> + PageTable[Index] = (UINT64)(UINTN)NewPageTable |
> IA32_PG_P | IA32_PG_RW;
> PageTable = NewPageTable;
> }
> @@ -440,7 +440,7 @@ Split1GPageTo2M (
> // Fill in 1G page entry.
> //
> *PageEntry1G = ((UINT64)(UINTN)PageDirectoryEntry |
> - IA32_PG_P | IA32_PG_RW | AddressEncMask);
> + IA32_PG_P | IA32_PG_RW);
>
> PhysicalAddress2M = PhysicalAddress;
> for (IndexOfPageDirectoryEntries = 0; @@ -616,7 +616,7 @@
> InternalMemEncryptSevCreateIdentityMap1G (
> }
>
> SetMem (NewPageTable, EFI_PAGE_SIZE, 0);
> - PageMapLevel4Entry->Uint64 = (UINT64)(UINTN)NewPageTable | AddressEncMask;
> + PageMapLevel4Entry->Uint64 = (UINT64)(UINTN)NewPageTable;
> PageMapLevel4Entry->Bits.MustBeZero = 0;
> PageMapLevel4Entry->Bits.ReadWrite = 1;
> PageMapLevel4Entry->Bits.Present = 1;
prev parent reply other threads:[~2023-06-29 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 5:23 [Patch V7 00/14] Use CpuPageTableLib to create and update smm page table duntan
2023-06-27 5:23 ` [Patch V7 01/14] OvmfPkg:Remove code that apply AddressEncMask to non-leaf entry duntan
2023-06-27 13:13 ` Lendacky, Thomas
2023-06-29 10:09 ` duntan [this message]
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=BN9PR11MB5483A573CFA38E5087824639E525A@BN9PR11MB5483.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