Re: [edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-19 Thread Ashish Kalra via groups.io
Hello Tom, On Fri, Jul 16, 2021 at 09:11:23AM -0500, Tom Lendacky wrote: > On 7/8/21 9:07 AM, Ashish Kalra wrote: > > From: Ashish Kalra > > > > The patch subject is a bit confusing. Something more like "Add API to > issue hypercall on page encryption state change" or similar, since this is >

Re: [edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-19 Thread Ashish Kalra via groups.io
Hello Dov, On Mon, Jul 19, 2021 at 11:04:17AM +0300, Dov Murik wrote: > > > On 16/07/2021 15:29, Ashish Kalra wrote: > > Hello Dov, > > > > On Thu, Jul 15, 2021 at 11:58:17PM +0300, Dov Murik wrote: > >> Hi Ashish, > >> > >> On 08/07/2021 17:07, Ashish Kalra wrote: > >>> From: Ashish Kalra >

Re: [edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-19 Thread Dov Murik
On 16/07/2021 15:29, Ashish Kalra wrote: > Hello Dov, > > On Thu, Jul 15, 2021 at 11:58:17PM +0300, Dov Murik wrote: >> Hi Ashish, >> >> On 08/07/2021 17:07, Ashish Kalra wrote: >>> From: Ashish Kalra >>> >>> By default all the SEV guest memory regions are considered encrypted, >>> if a guest

Re: [edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-16 Thread Lendacky, Thomas via groups.io
On 7/8/21 9:07 AM, Ashish Kalra wrote: > From: Ashish Kalra > The patch subject is a bit confusing. Something more like "Add API to issue hypercall on page encryption state change" or similar, since this is issued for changes to shared and private, not just shared. > By default all the SEV

Re: [edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-16 Thread Ashish Kalra via groups.io
Hello Dov, On Thu, Jul 15, 2021 at 11:58:17PM +0300, Dov Murik wrote: > Hi Ashish, > > On 08/07/2021 17:07, Ashish Kalra wrote: > > From: Ashish Kalra > > > > By default all the SEV guest memory regions are considered encrypted, > > if a guest changes the encryption attribute of the page (e.g

Re: [edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-15 Thread Dov Murik
Hi Ashish, On 08/07/2021 17:07, Ashish Kalra wrote: > From: Ashish Kalra > > By default all the SEV guest memory regions are considered encrypted, > if a guest changes the encryption attribute of the page (e.g mark a > page as decrypted) then notify hypervisor. Hypervisor will need to > track

[edk2-devel] [PATCH v5 1/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall

2021-07-08 Thread Ashish Kalra via groups.io
From: Ashish Kalra By default all the SEV guest memory regions are considered encrypted, if a guest changes the encryption attribute of the page (e.g mark a page as decrypted) then notify hypervisor. Hypervisor will need to track the unencrypted pages. The information will be used during guest