Re: [PATCH v6 3/5] x86/mm: add .data..decrypted section to hold shared variables

2018-09-10 Thread Brijesh Singh
On 9/10/18 6:54 AM, Borislav Petkov wrote: ... >> @@ -487,28 +510,69 @@ static void __init teardown_workarea_map(struct >> sme_workarea_data *wa, >> native_write_cr3(__native_read_cr3()); >> } >> >> +static void __init decrypt_shared_data(struct sme_workarea_data *wa, >> +

Re: [PATCH v6 3/5] x86/mm: add .data..decrypted section to hold shared variables

2018-09-10 Thread Brijesh Singh
On 9/10/18 6:54 AM, Borislav Petkov wrote: ... >> @@ -487,28 +510,69 @@ static void __init teardown_workarea_map(struct >> sme_workarea_data *wa, >> native_write_cr3(__native_read_cr3()); >> } >> >> +static void __init decrypt_shared_data(struct sme_workarea_data *wa, >> +

Re: [PATCH v6 3/5] x86/mm: add .data..decrypted section to hold shared variables

2018-09-10 Thread Borislav Petkov
On Fri, Sep 07, 2018 at 12:57:28PM -0500, Brijesh Singh wrote: > kvmclock defines few static variables which are shared with the > hypervisor during the kvmclock initialization. > > When SEV is active, memory is encrypted with a guest-specific key, and > if guest OS wants to share the memory

Re: [PATCH v6 3/5] x86/mm: add .data..decrypted section to hold shared variables

2018-09-10 Thread Borislav Petkov
On Fri, Sep 07, 2018 at 12:57:28PM -0500, Brijesh Singh wrote: > kvmclock defines few static variables which are shared with the > hypervisor during the kvmclock initialization. > > When SEV is active, memory is encrypted with a guest-specific key, and > if guest OS wants to share the memory

[PATCH v6 3/5] x86/mm: add .data..decrypted section to hold shared variables

2018-09-07 Thread Brijesh Singh
kvmclock defines few static variables which are shared with the hypervisor during the kvmclock initialization. When SEV is active, memory is encrypted with a guest-specific key, and if guest OS wants to share the memory region with hypervisor then it must clear the C-bit before sharing it.

[PATCH v6 3/5] x86/mm: add .data..decrypted section to hold shared variables

2018-09-07 Thread Brijesh Singh
kvmclock defines few static variables which are shared with the hypervisor during the kvmclock initialization. When SEV is active, memory is encrypted with a guest-specific key, and if guest OS wants to share the memory region with hypervisor then it must clear the C-bit before sharing it.