Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2023-01-12 Thread Yao, Jiewen
ndacky ; Ni, > Ray > Subject: Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV- > SNP CC blob as EfiACPIReclaimMemory > > On Sat, 7 Jan 2023 at 03:01, Yao, Jiewen wrote: > > > > Hi Dov/Ard > > Please allow me to clarify: > > > > EfiACPIRecl

Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2023-01-07 Thread Ard Biesheuvel
On Sat, 7 Jan 2023 at 03:01, Yao, Jiewen wrote: > > Hi Dov/Ard > Please allow me to clarify: > > EfiACPIReclaimMemory in UEFI spec means: OS may use the memory, after it > copies the ACPI table to its own location. It is also called > "AddressRangeACPI" in ACPI spec. > > [2] https://uefi.org/spe

Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2023-01-06 Thread Yao, Jiewen
Lendacky ; Ni, Ray > ; Dov Murik > Subject: Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV- > SNP CC blob as EfiACPIReclaimMemory > > Hi Jiewen, > > On 06/01/2023 11:18, Yao, Jiewen wrote: > > Are you sure you want to use EfiACPIReclaimMemory ? > > >

Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2023-01-06 Thread Dov Murik
m: devel@edk2.groups.io On Behalf Of Roth, >> Michael via groups.io >> Sent: Thursday, December 22, 2022 12:07 AM >> To: devel@edk2.groups.io >> Cc: Tom Lendacky ; Ni, Ray >> ; Dov Murik >> Subject: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC >

Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2023-01-06 Thread Yao, Jiewen
.groups.io > Cc: Tom Lendacky ; Ni, Ray > ; Dov Murik > Subject: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC > blob as EfiACPIReclaimMemory > > The SEV-SNP Confidential Computing blob contains metadata that should > remain accessible for the life of the gue

Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2022-12-21 Thread Dov Murik
Thanks Mike for fixing this. On 21/12/2022 18:06, Michael Roth wrote: > The SEV-SNP Confidential Computing blob contains metadata that should > remain accessible for the life of the guest. Allocate it as > EfiACPIReclaimMemory to ensure the memory isn't overwritten by the guest > operating system

[edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2022-12-21 Thread Roth, Michael via groups.io
The SEV-SNP Confidential Computing blob contains metadata that should remain accessible for the life of the guest. Allocate it as EfiACPIReclaimMemory to ensure the memory isn't overwritten by the guest operating system later. Reported-by: Dov Murik Suggested-by: Dov Murik Signed-off-by: Michael

Re: [edk2-devel] [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory

2022-12-21 Thread Lendacky, Thomas via groups.io
On 12/21/22 10:06, Michael Roth wrote: The SEV-SNP Confidential Computing blob contains metadata that should remain accessible for the life of the guest. Allocate it as EfiACPIReclaimMemory to ensure the memory isn't overwritten by the guest operating system later. Reported-by: Dov Murik Sugges