Re: [Part1 PATCH v5 16/17] X86/KVM: Decrypt shared per-cpu variables when SEV is active

2017-09-28 Thread Borislav Petkov
On Wed, Sep 27, 2017 at 10:13:28AM -0500, Brijesh Singh wrote: > When SEV is active, guest memory is encrypted with a guest-specific key, a > guest memory region shared with the hypervisor must be mapped as decrypted > before we can share it. > > Cc: Thomas Gleixner > Cc:

Re: [Part1 PATCH v5 16/17] X86/KVM: Decrypt shared per-cpu variables when SEV is active

2017-09-28 Thread Borislav Petkov
On Wed, Sep 27, 2017 at 10:13:28AM -0500, Brijesh Singh wrote: > When SEV is active, guest memory is encrypted with a guest-specific key, a > guest memory region shared with the hypervisor must be mapped as decrypted > before we can share it. > > Cc: Thomas Gleixner > Cc: Ingo Molnar > Cc: "H.

[Part1 PATCH v5 16/17] X86/KVM: Decrypt shared per-cpu variables when SEV is active

2017-09-27 Thread Brijesh Singh
When SEV is active, guest memory is encrypted with a guest-specific key, a guest memory region shared with the hypervisor must be mapped as decrypted before we can share it. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc:

[Part1 PATCH v5 16/17] X86/KVM: Decrypt shared per-cpu variables when SEV is active

2017-09-27 Thread Brijesh Singh
When SEV is active, guest memory is encrypted with a guest-specific key, a guest memory region shared with the hypervisor must be mapped as decrypted before we can share it. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Borislav Petkov Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: