From: Joerg Roedel <joerg.roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, Jan Kiszka <jan.kiszka@web.de>,
kvm-devel list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: List of unaccessible x86 states
Date: Mon, 26 Oct 2009 10:17:31 +0100 [thread overview]
Message-ID: <20091026091731.GF5326@amd.com> (raw)
In-Reply-To: <4AE41F2F.2050700@redhat.com>
On Sun, Oct 25, 2009 at 11:49:35AM +0200, Avi Kivity wrote:
> On 10/24/2009 12:35 PM, Alexander Graf wrote:
> >
> >Hm, thinking about this again, it might be useful to have an
> >"currently in nested VM" flag here. That way userspace can decide
> >if it needs to get out of the nested state (for migration) or if
> >it just doesn't care.
>
> Getting out of nested state involves modifying state (both memory
> and registers). Nor can we in the general case force it. The guest
> can set up a situation where it is impossible to #vmexit.
There is actually more than that. If the guest runs in guest mode itself
we also need to report the host state to be able to do an #vmexit after
migration.
In nested SVM the host state is not saved in the guest memory to prevent
the guest from modifying it and break out of its virtualization jail.
Joerg
next prev parent reply other threads:[~2009-10-26 9:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 13:01 List of unaccessible x86 states Jan Kiszka
2009-10-20 13:10 ` Alexander Graf
2009-10-20 13:19 ` Jan Kiszka
2009-10-20 13:27 ` Gleb Natapov
2009-10-20 13:29 ` Jan Kiszka
2009-10-20 13:32 ` Gleb Natapov
2009-10-20 13:27 ` Alexander Graf
2009-10-20 13:37 ` Jan Kiszka
2009-10-20 13:41 ` Alexander Graf
2009-10-20 13:48 ` Gleb Natapov
2009-10-20 13:51 ` Alexander Graf
2009-10-20 18:55 ` Gleb Natapov
2009-10-20 18:59 ` Alexander Graf
2009-10-20 19:09 ` Gleb Natapov
2009-10-20 19:23 ` Alexander Graf
2009-10-20 19:31 ` Gleb Natapov
2009-10-25 9:46 ` Avi Kivity
2009-10-25 13:53 ` Alexander Graf
2009-10-25 14:08 ` Avi Kivity
2009-10-25 16:45 ` Alexander Graf
2009-10-26 8:33 ` Avi Kivity
2009-10-26 9:11 ` Alexander Graf
2009-10-26 9:19 ` Avi Kivity
2009-10-20 13:35 ` Gleb Natapov
2009-10-20 18:45 ` Marcelo Tosatti
2009-10-23 13:08 ` Jan Kiszka
2009-10-23 17:00 ` Marcelo Tosatti
2009-10-23 19:26 ` Jan Kiszka
2009-10-23 19:34 ` Jan Kiszka
2009-10-24 10:35 ` Alexander Graf
2009-10-25 9:49 ` Avi Kivity
2009-10-26 9:17 ` Joerg Roedel [this message]
2009-10-26 9:21 ` Avi Kivity
2009-10-26 9:30 ` Joerg Roedel
2009-10-26 9:39 ` Avi Kivity
2009-10-26 9:56 ` Joerg Roedel
2009-10-26 10:09 ` Avi Kivity
2009-10-26 10:45 ` Joerg Roedel
2009-10-26 10:56 ` Avi Kivity
2009-10-26 11:10 ` 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=20091026091731.GF5326@amd.com \
--to=joerg.roedel@amd.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.