Re: [edk2-devel] [PATCH v2 0/2] SEV BaseMemEncryptLib cleanup

2022-02-27 Thread Yao, Jiewen
> Tom Lendacky ; Justen, Jordan L > ; Ard Biesheuvel ; > Aktas, Erdem ; Michael Roth > ; Gerd Hoffmann ; > aaron.yo...@oracle.com > Subject: Re: [edk2-devel] [PATCH v2 0/2] SEV BaseMemEncryptLib cleanup > > Acked-by: Jiewen Yao > > > -Original Message- > &

Re: [edk2-devel] [PATCH v2 0/2] SEV BaseMemEncryptLib cleanup

2022-02-27 Thread Yao, Jiewen
Acked-by: Jiewen Yao > -Original Message- > From: Brijesh Singh > Sent: Monday, February 21, 2022 10:59 PM > To: devel@edk2.groups.io > Cc: James Bottomley ; Xu, Min M ; > Yao, Jiewen ; Tom Lendacky > ; Justen, Jordan L ; > Ard Biesheuvel ; Aktas, Erdem > ; Michael Roth ; Gerd >

[edk2-devel] [PATCH v2 0/2] SEV BaseMemEncryptLib cleanup

2022-02-21 Thread Brijesh Singh via groups.io
This is the first of cleanup for SEV MemEncryptLib. The library uses the CPUID followed by the MSR read to determine whether SEV is enabled. Now that we have a workarea concept, the logic can be simplified to store the msr status in workarea and use that to build PCDs and then later simply use