From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: List of unaccessible x86 states Date: Mon, 26 Oct 2009 11:39:46 +0200 Message-ID: <4AE56E62.2050509@redhat.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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Jan Kiszka , kvm-devel list , Marcelo Tosatti , Gleb Natapov To: Joerg Roedel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22140 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755330AbZJZJjr (ORCPT ); Mon, 26 Oct 2009 05:39:47 -0400 In-Reply-To: <20091026093020.GG5326@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function