.groups.io
> Cc: brijesh.si...@amd.com; James Bottomley ; Xu, Min M
> ; Tom Lendacky ; Justen,
> Jordan L ; Ard Biesheuvel
> ; Erdem Aktas ;
> Michael Roth
> Subject: Re: [edk2-devel] [PATCH 0/3] reuse the SevEsWork area
>
> Hi Jiewen,
>
> On 8/4/21 9:18 PM, Yao, Ji
4:20 AM
To: devel@edk2.groups.io
Cc: James Bottomley ; Xu, Min M ;
Yao, Jiewen ; Tom Lendacky
; Justen, Jordan L ;
Ard Biesheuvel ; Erdem Aktas
; Michael Roth ; Brijesh
Singh
Subject: [edk2-devel] [PATCH 0/3] reuse the SevEsWork area
Based on the discussion on the mailing list, we agreed that
ups.io On Behalf Of Brijesh
>> Singh via groups.io
>> Sent: Thursday, August 5, 2021 4:20 AM
>> To: devel@edk2.groups.io
>> Cc: James Bottomley ; Xu, Min M ;
>> Yao, Jiewen ; Tom Lendacky
>> ; Justen, Jordan L ;
>> Ard Biesheuvel ; Erdem Aktas
>> ; Mi
Brijesh
> Singh via groups.io
> Sent: Thursday, August 5, 2021 4:20 AM
> To: devel@edk2.groups.io
> Cc: James Bottomley ; Xu, Min M ;
> Yao, Jiewen ; Tom Lendacky
> ; Justen, Jordan L ;
> Ard Biesheuvel ; Erdem Aktas
> ; Michael Roth ; Brijesh
> Singh
> Subject: [ed
Based on the discussion on the mailing list, we agreed that instead
of wasting extra page in the MEMFD, we can reuse the SevEsWorkArea
buffer for the TDX. To avoid any confusion, lets introduce a OvmfWorkArea
that will contains 32 bytes of header followed by the actual workarea.
While at it, move
