Re: [PATCH 1/2] x86/mm: add .data..decrypted section to hold shared variables

2018-08-28 Thread Brijesh Singh
On 08/27/2018 05:11 PM, Tom Lendacky wrote: On 08/27/2018 06:24 AM, Brijesh Singh wrote: kvmclock defines few static variables which are shared with hypervisor during the kvmclock initialization. When SEV is active, memory is encrypted with a guest-specific key, and if guest OS wants to shar

Re: [PATCH 1/2] x86/mm: add .data..decrypted section to hold shared variables

2018-08-27 Thread Tom Lendacky
On 08/27/2018 06:24 AM, Brijesh Singh wrote: > kvmclock defines few static variables which are shared with 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

[PATCH 1/2] x86/mm: add .data..decrypted section to hold shared variables

2018-08-27 Thread Brijesh Singh
kvmclock defines few static variables which are shared with 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. The '__dec