qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Kauer <kauer@os.inf.tu-dresden.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] allow update of MSR_EFER_SVM
Date: Fri, 29 Feb 2008 10:41:13 +0100	[thread overview]
Message-ID: <20080229094113.GB9305@chrom.inf.tu-dresden.de> (raw)
In-Reply-To: <50E1BA25-AC2A-48A2-AFF2-83630AE4BF9E@csgraf.de>

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

On Wed, Feb 27, 2008 at 06:03:49PM +0100, Alexander Graf wrote:
> MSR_EFER_SVM is not defined in my qemu version. What does the bit change 
> if set?

The AMD vol2 reads like this:

	Secure Virtual Machine Enable (SVME) Bit. Bit 12. Enables the SVM extensions.
	When this bit is zero, the SVM instructions cause #UD exceptions.

The bit was called MSR_EFER_SVME_MASK in svm.h before, I renamed it in the
attached patch to MSR_EFER_SVME to match the style of the other definitions
in cpu.h.

BTW, triggering the above mentioned #UD is missing in the code...


	Bernhard Kauer

[-- Attachment #2: qemu_efer.diff --]
[-- Type: text/x-diff, Size: 1201 bytes --]

Index: target-i386/helper.c
===================================================================
RCS file: /sources/qemu/qemu/target-i386/helper.c,v
retrieving revision 1.101
diff -u -r1.101 helper.c
--- target-i386/helper.c	3 Feb 2008 03:26:30 -0000	1.101
+++ target-i386/helper.c	29 Feb 2008 09:33:41 -0000
@@ -2802,6 +2802,8 @@
                 update_mask |= MSR_EFER_FFXSR;
             if (env->cpuid_ext2_features & CPUID_EXT2_NX)
                 update_mask |= MSR_EFER_NXE;
+	    if (env->cpuid_ext3_features & CPUID_EXT3_SVM)
+	        update_mask |= MSR_EFER_SVME;
             env->efer = (env->efer & ~update_mask) |
             (val & update_mask);
         }
Index: target-i386/svm.h
===================================================================
RCS file: /sources/qemu/qemu/target-i386/svm.h,v
retrieving revision 1.1
diff -u -r1.1 svm.h
--- target-i386/svm.h	23 Sep 2007 15:30:28 -0000	1.1
+++ target-i386/svm.h	29 Feb 2008 09:33:41 -0000
@@ -179,7 +179,7 @@
 #define SVM_CPUID_FEATURE_SHIFT 2
 #define SVM_CPUID_FUNC 0x8000000a
 
-#define MSR_EFER_SVME_MASK (1ULL << 12)
+#define MSR_EFER_SVME  (1ULL << 12)
 
 #define SVM_SELECTOR_S_SHIFT 4
 #define SVM_SELECTOR_DPL_SHIFT 5

  reply	other threads:[~2008-02-29  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 16:07 [Qemu-devel] [PATCH] allow update of MSR_EFER_SVM Bernhard Kauer
2008-02-27 17:03 ` Alexander Graf
2008-02-29  9:41   ` Bernhard Kauer [this message]
2008-02-29 10:20     ` Alexander Graf
2008-02-29 15:43       ` Bernhard Kauer

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=20080229094113.GB9305@chrom.inf.tu-dresden.de \
    --to=kauer@os.inf.tu-dresden.de \
    --cc=qemu-devel@nongnu.org \
    /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).