public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Avi Kivity <avi@redhat.com>
Cc: Zachary Amsden <zamsden@redhat.com>,
	Joerg Roedel <joerg.roedel@amd.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Nested SVM and migration
Date: Sun, 21 Feb 2010 14:09:15 +0100	[thread overview]
Message-ID: <20100221130915.GB26465@8bytes.org> (raw)
In-Reply-To: <4B812CE9.2070107@redhat.com>

On Sun, Feb 21, 2010 at 02:54:01PM +0200, Avi Kivity wrote:
> So, if some other cpu (or the guest itself, with appropriate  
> permissions) modifies the msr permission bitmap, svm will not notice  
> this?  svm loads the bitmap during entry?

Yes.

> I don't think you can tell, unless the host cpu modifying the vmcb is  
> synchronized with the guest (or the guest modifies its own vmcb).  But  
> this is all academic.

Hmm, another thing comes to mind. We would need some redesign of the
nested_svm code to allow userspace to put a vcpu directly into nested
state. With the MSR approach, all userspace does is to write MSRs into
the vcpu before the first run?

	Joerg


  reply	other threads:[~2010-02-21 13:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 19:14 Nested SVM and migration Zachary Amsden
2010-02-20 20:18 ` Joerg Roedel
2010-02-20 23:26   ` Zachary Amsden
2010-02-21 12:10     ` Joerg Roedel
2010-02-21 12:24       ` Avi Kivity
2010-02-21 12:41         ` Joerg Roedel
2010-02-21 12:54           ` Avi Kivity
2010-02-21 13:09             ` Joerg Roedel [this message]
2010-02-21 13:14               ` Avi Kivity
     [not found]                 ` <4B8137E7.4030001@redhat.com>
     [not found]                   ` <20100221144352.GC26465@8bytes.org>
2010-02-22 16:54                     ` Zachary Amsden
     [not found]                     ` <4B814C41.7010105@redhat.com>
     [not found]                       ` <20100221155624.GD26465@8bytes.org>
2010-02-22 16:56                         ` Zachary Amsden
2010-02-22 16:59                           ` Avi Kivity
2010-02-22 16:46               ` Zachary Amsden
2010-02-22 17:07                 ` Joerg Roedel
2010-02-24 15:23               ` Joerg Roedel
2010-02-24 20:21                 ` Zachary Amsden
2010-02-22 16:42         ` Zachary Amsden
2010-02-22 16:44           ` Avi Kivity
2010-02-22 17:00             ` Zachary Amsden
2010-02-22 17:02               ` Avi Kivity
2010-02-22 17:07                 ` Zachary Amsden
2010-02-22 17:11                   ` Avi Kivity
2010-02-22 17:24                     ` Zachary Amsden
2010-02-22 16:39       ` Zachary Amsden
2010-02-21  7:23   ` Avi Kivity
2010-02-21  7:46     ` Gleb Natapov
2010-02-21  8:12       ` Avi Kivity
2010-02-21 12:18     ` Joerg Roedel

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=20100221130915.GB26465@8bytes.org \
    --to=joro@8bytes.org \
    --cc=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=zamsden@redhat.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