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 16:43:14 +0100	[thread overview]
Message-ID: <20080229154314.GA31173@chrom.inf.tu-dresden.de> (raw)
In-Reply-To: <F91079F9-C033-4112-B905-56FD6CA85882@csgraf.de>

On Fri, Feb 29, 2008 at 11:20:24AM +0100, Alexander Graf wrote:
> Keep in mind that updating the bit should fail within a virtual machine.

I found the following sentence in the manual:

	The effect of turning off EFER.SVME while a guest is running is undefined;
	therefore, the VMM should always prevent guests from writing EFER.

Therefore i think the wrmsr-code is just fine, as it is in my patch.


	Bernhard Kauer

      reply	other threads:[~2008-02-29 15:43 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
2008-02-29 10:20     ` Alexander Graf
2008-02-29 15:43       ` Bernhard Kauer [this message]

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=20080229154314.GA31173@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).