| Date | Fri, 20 Oct 2017 17:00:38 +0200 | From | Borislav Petkov <> | Subject | Re: [Part2 PATCH v6 08/38] KVM: Introduce KVM_MEMORY_ENCRYPT_{UN,}REG_REGION ioctl |
| |
On Thu, Oct 19, 2017 at 09:33:43PM -0500, Brijesh Singh wrote: > If hardware supports memory encryption then KVM_MEMORY_ENCRYPT_REG_REGION > and KVM_MEMORY_ENCRYPT_UNREG_REGION ioctl's can be used by userspace to > register/unregister the guest memory regions which may contain the encrypted > data (e.g guest RAM, PCI BAR, SMRAM etc). > > Cc: Thomas Gleixner <tglx@linutronix.de> > Cc: Ingo Molnar <mingo@redhat.com> > Cc: "H. Peter Anvin" <hpa@zytor.com> > Cc: Paolo Bonzini <pbonzini@redhat.com> > Cc: "Radim Krčmář" <rkrcmar@redhat.com> > Cc: Joerg Roedel <joro@8bytes.org> > Cc: Borislav Petkov <bp@suse.de> > Cc: Tom Lendacky <thomas.lendacky@amd.com> > Cc: x86@kernel.org > Cc: kvm@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> > --- > Documentation/virtual/kvm/api.txt | 34 ++++++++++++++++++++++++++++++++++ > arch/x86/include/asm/kvm_host.h | 2 ++ > arch/x86/kvm/x86.c | 24 ++++++++++++++++++++++++ > include/uapi/linux/kvm.h | 8 ++++++++ > 4 files changed, 68 insertions(+)
Reviewed-by: Borislav Petkov <bp@suse.de> Improvements-by: Borislav Petkov <bp@suse.de>
-- Regards/Gruss, Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
|