qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brijesh Singh <brijesh.singh@amd.com>
To: qemu-devel@nongnu.org
Cc: Alistair Francis <alistair.francis@xilinx.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Eric Blake <eblake@redhat.com>,
	kvm@vger.kernel.org, Marcel Apfelbaum <marcel@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Richard Henderson <richard.henderson@linaro.org>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Thomas Lendacky <Thomas.Lendacky@amd.com>,
	Borislav Petkov <bp@suse.de>,
	Brijesh Singh <brijesh.singh@amd.com>
Subject: [Qemu-devel] [PATCH v7 21/26] sev: add debug encrypt and decrypt commands
Date: Wed,  7 Feb 2018 10:06:33 -0600	[thread overview]
Message-ID: <20180207160638.98872-21-brijesh.singh@amd.com> (raw)
In-Reply-To: <20180207160638.98872-1-brijesh.singh@amd.com>

KVM_SEV_DBG_DECRYPT and KVM_SEV_DBG_ENCRYPT commands are used for
decrypting and encrypting guest memory region. The command works only if
the guest policy allows the debugging.

Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
---
 accel/kvm/kvm-all.c    |  1 +
 accel/kvm/sev.c        | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++
 accel/kvm/trace-events |  1 +
 include/sysemu/sev.h   |  1 +
 4 files changed, 75 insertions(+)

diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
index 37f7c442dc3f..7d3b7b4107eb 100644
--- a/accel/kvm/kvm-all.c
+++ b/accel/kvm/kvm-all.c
@@ -1677,6 +1677,7 @@ static int kvm_init(MachineState *ms)
         }
 
         kvm_state->memcrypt_encrypt_data = sev_encrypt_data;
+        kvm_state->memcrypt_debug_ops = sev_set_debug_ops;
     }
 
     ret = kvm_arch_init(ms, s);
diff --git a/accel/kvm/sev.c b/accel/kvm/sev.c
index e422f43caa0b..7b57575e2f93 100644
--- a/accel/kvm/sev.c
+++ b/accel/kvm/sev.c
@@ -23,11 +23,13 @@
 
 #define DEFAULT_GUEST_POLICY    0x1 /* disable debug */
 #define DEFAULT_SEV_DEVICE      "/dev/sev"
+#define GUEST_POLICY_DBG_BIT    0x1
 
 static uint64_t me_mask;
 static bool sev_active;
 static int sev_fd;
 static SEVState *sev_state;
+static MemoryRegionRAMReadWriteOps  sev_ops;
 
 #define SEV_FW_MAX_ERROR      0x17
 
@@ -575,6 +577,51 @@ sev_vm_state_change(void *opaque, int running, RunState state)
     }
 }
 
+static int
+sev_dbg_enc_dec(uint8_t *dst, const uint8_t *src, uint32_t len, bool write)
+{
+    int ret, error;
+    struct kvm_sev_dbg *dbg;
+
+    dbg = g_malloc0(sizeof(*dbg));
+    if (!dbg) {
+        return 1;
+    }
+
+    dbg->src_uaddr = (unsigned long)src;
+    dbg->dst_uaddr = (unsigned long)dst;
+    dbg->len = len;
+
+    trace_kvm_sev_debug(write ? "encrypt" : "decrypt", src, dst, len);
+    ret = sev_ioctl(write ? KVM_SEV_DBG_ENCRYPT : KVM_SEV_DBG_DECRYPT,
+                    dbg, &error);
+    if (ret) {
+        error_report("%s (%s) %#llx->%#llx+%#x ret=%d fw_error=%d '%s'",
+                     __func__, write ? "write" : "read", dbg->src_uaddr,
+                     dbg->dst_uaddr, dbg->len, ret, error,
+                     fw_error_to_str(error));
+    }
+
+    g_free(dbg);
+    return ret;
+}
+
+static int
+sev_mem_read(uint8_t *dst, const uint8_t *src, uint32_t len, MemTxAttrs attrs)
+{
+    assert(attrs.debug);
+
+    return sev_dbg_enc_dec(dst, src, len, false);
+}
+
+static int
+sev_mem_write(uint8_t *dst, const uint8_t *src, uint32_t len, MemTxAttrs attrs)
+{
+    assert(attrs.debug);
+
+    return sev_dbg_enc_dec(dst, src, len, true);
+}
+
 void *
 sev_guest_init(const char *id)
 {
@@ -651,6 +698,31 @@ sev_encrypt_data(void *handle, uint8_t *ptr, uint64_t len)
     return 0;
 }
 
+void
+sev_set_debug_ops(void *handle, MemoryRegion *mr)
+{
+    int policy;
+    SEVState *s = (SEVState *)handle;
+
+    policy = object_property_get_int(OBJECT(s->sev_info),
+                                     "policy", &error_abort);
+
+    /*
+     * Check if guest policy supports debugging
+     * Bit 0 :
+     *   0 - debug allowed
+     *   1 - debug is not allowed
+     */
+    if (policy & GUEST_POLICY_DBG_BIT) {
+        return;
+    }
+
+    sev_ops.read = sev_mem_read;
+    sev_ops.write = sev_mem_write;
+
+    memory_region_set_ram_debug_ops(mr, &sev_ops);
+}
+
 static void
 sev_register_types(void)
 {
diff --git a/accel/kvm/trace-events b/accel/kvm/trace-events
index e810d75ea1b3..de6a12c51e06 100644
--- a/accel/kvm/trace-events
+++ b/accel/kvm/trace-events
@@ -22,3 +22,4 @@ kvm_sev_launch_start(int policy, void *session, void *pdh) "policy 0x%x session
 kvm_sev_launch_update_data(void *addr, uint64_t len) "addr %p len 0x%" PRIu64
 kvm_sev_launch_measurement(const char *value) "data %s"
 kvm_sev_launch_finish(void) ""
+kvm_sev_debug(const char *op, const uint8_t *src, uint8_t *dst, int len) "(%s) src %p dst %p len %d"
diff --git a/include/sysemu/sev.h b/include/sysemu/sev.h
index c173ad33f8bb..186ebca0f945 100644
--- a/include/sysemu/sev.h
+++ b/include/sysemu/sev.h
@@ -78,6 +78,7 @@ typedef struct SEVState SEVState;
 
 void *sev_guest_init(const char *id);
 int sev_encrypt_data(void *handle, uint8_t *ptr, uint64_t len);
+void sev_set_debug_ops(void *handle, MemoryRegion *mr);
 
 #endif
 
-- 
2.14.3

  parent reply	other threads:[~2018-02-07 16:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 16:06 [Qemu-devel] [PATCH v7 01/26] memattrs: add debug attribute Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 02/26] exec: add ram_debug_ops support Brijesh Singh
2018-02-07 16:19   ` Eric Blake
2018-02-07 16:33     ` Brijesh Singh
2018-02-07 16:46       ` Eric Blake
2018-02-07 16:51   ` Paolo Bonzini
2018-02-07 20:26     ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 03/26] exec: add debug version of physical memory read and write API Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 04/26] monitor/i386: use debug APIs when accessing guest memory Brijesh Singh
2018-02-07 16:53   ` Paolo Bonzini
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 05/26] target/i386: add memory encryption feature cpuid support Brijesh Singh
2018-02-07 16:54   ` Paolo Bonzini
2018-02-07 18:28     ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 06/26] machine: add -memory-encryption property Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 07/26] kvm: update kvm.h to include memory encryption ioctls Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 08/26] docs: add AMD Secure Encrypted Virtualization (SEV) Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 09/26] accel: add Secure Encrypted Virtulization (SEV) object Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 10/26] sev: add command to initialize the memory encryption context Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 11/26] sev: register the guest memory range which may contain encrypted data Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 12/26] kvm: introduce memory encryption APIs Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 13/26] qmp: add query-sev command Brijesh Singh
2018-02-07 16:22   ` Eric Blake
2018-02-07 16:36     ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 14/26] hmp: add 'info sev' command Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 15/26] sev: add command to create launch memory encryption context Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 16/26] sev: add command to encrypt guest memory region Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 17/26] target/i386: encrypt bios rom Brijesh Singh
2018-02-09 18:28   ` Dr. David Alan Gilbert
2018-02-09 20:49     ` Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 18/26] sev: add support to LAUNCH_MEASURE command Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 19/26] sev: Finalize the SEV guest launch flow Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 20/26] hw: i386: set ram_debug_ops when memory encryption is enabled Brijesh Singh
2018-02-07 16:06 ` Brijesh Singh [this message]
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 22/26] target/i386: clear C-bit when walking SEV guest page table Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 23/26] include: add psp-sev.h header file Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 25/26] sev: add support to KVM_SEV_GUEST_STATUS Brijesh Singh
2018-02-07 16:06 ` [Qemu-devel] [PATCH v7 26/26] qmp: add query-sev-launch-measure command Brijesh Singh
2018-02-07 16:29   ` Eric Blake
2018-02-07 18:12     ` Brijesh Singh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180207160638.98872-21-brijesh.singh@amd.com \
    --to=brijesh.singh@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=alistair.francis@xilinx.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=bp@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).