From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: List of unaccessible x86 states
Date: Sun, 25 Oct 2009 11:49:35 +0200
Message-ID: <4AE41F2F.2050700@redhat.com>
References: <4ADDB49B.3010101@siemens.com> <4AE2055A.3050001@web.de> <9D81B6EA-7161-4682-8685-79928C0AC2B3@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jan Kiszka <jan.kiszka@web.de>,
	kvm-devel list <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	Joerg Roedel <joerg.roedel@amd.com>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:54197 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752434AbZJYJtg (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 25 Oct 2009 05:49:36 -0400
In-Reply-To: <9D81B6EA-7161-4682-8685-79928C0AC2B3@suse.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.

>> - KVM_X86_VCPU_STATE_SVM
>>    o gif
>
> Can we make this an "svm_flags" or so u32? And then we'd just set bits?
>

Or individual flags as u8s, so we don't get trapped into a specific 
encoding which is really an implementation detail.

-- 
error compiling committee.c: too many arguments to function