On 4/24/19 11:10 AM, Singh, Brijesh wrote:
> The hypercall can be used by the SEV guest to notify the page encryption
This hyercall is used by the SEV guest to notify a change in the page...
> status to the hypervisor. The hypercall should be invoked only when
> the encryption attribute is change
On 4/24/19 11:10 AM, Singh, Brijesh wrote:
> The command finalize the guest receiving process and make the SEV guest
> ready for the execution.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Joerg Roedel
> Cc: Borislav Petkov
On 4/24/19 11:10 AM, Singh, Brijesh wrote:
> The command is used for copying the incoming buffer into the
> SEV guest memory space.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Joerg Roedel
> Cc: Borislav Petkov
> Cc: Tom Le
On 4/24/19 11:10 AM, Singh, Brijesh wrote:
> The command is used to create encryption context for the incoming
create the encryption context for an incoming
> SEV guest. The encryption context can be later unused by the hypervisor
can be later used by
> to import the incoming data into the SEV
On 4/24/19 11:10 AM, Singh, Brijesh wrote:
> The command is used for encrypting the guest memory region using the
> encryption
> context created with KVM_SEV_SEND_START.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Joerg Roed
On 12/11/2018 02:53 PM, Eduardo Habkost wrote:
> The STIBP flag may be supported by the host KVM module, so QEMU
> can allow it to be configured manually, and it can be exposed to
> guests when using "-cpu host".
>
> No additional migration code is required because the whole
> contents of spec_ctr
