From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: List of unaccessible x86 states
Date: Mon, 26 Oct 2009 10:56:49 +0100
Message-ID: <20091026095649.GH5326@amd.com>
References: <4ADDB49B.3010101@siemens.com>
 <4AE2055A.3050001@web.de>
 <9D81B6EA-7161-4682-8685-79928C0AC2B3@suse.de>
 <4AE41F2F.2050700@redhat.com>
 <20091026091731.GF5326@amd.com>
 <4AE56A08.5090306@redhat.com>
 <20091026093020.GG5326@amd.com>
 <4AE56E62.2050509@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from tx2ehsobe003.messaging.microsoft.com ([65.55.88.13]:17737 "EHLO
	TX2EHSOBE006.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755460AbZJZJ5G (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 26 Oct 2009 05:57:06 -0400
Content-Disposition: inline
In-Reply-To: <4AE56E62.2050509@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Oct 26, 2009 at 11:39:46AM +0200, Avi Kivity wrote:
> On 10/26/2009 11:30 AM, Joerg Roedel wrote:
> >
> >>Which host state?  As far as I can tell, it can all be regenerated.
> >The state which is loaded into the vcpu when a #vmexit is emulated. This
> >includes segments, control registers and the host rip for example.
> 
> All of this state does not change between nested guest and normal
> guest mode.

I am talking about all the state that is saved in svm->nested.hsave.
When we migrate a guest vcpu while it is running in guest mode itself
(without forcing a nested #vmexit) this state is required when a #vmexit
needs to be emulated on this vcpu after migration.
Same is true for the nested intercept conditions.

	Joerg