From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: List of unaccessible x86 states Date: Tue, 20 Oct 2009 15:37:29 +0200 Message-ID: <4ADDBD19.6040107@siemens.com> References: <4ADDB49B.3010101@siemens.com> <5D3F39A4-0532-4027-8D71-87FE9BCA1C27@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm-devel , Avi Kivity , Marcelo Tosatti , Gleb Natapov To: Alexander Graf , oritw@il.ibm.com Return-path: Received: from goliath.siemens.de ([192.35.17.28]:17225 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752021AbZJTNhl (ORCPT ); Tue, 20 Oct 2009 09:37:41 -0400 In-Reply-To: <5D3F39A4-0532-4027-8D71-87FE9BCA1C27@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: > On 20.10.2009, at 15:01, Jan Kiszka wrote: > >> Hi all, >> >> as the list of yet user-unaccessible x86 states is a bit volatile ATM, >> this is an attempt to collect the precise requirements for additional >> state fields. Once everyone feels the list is complete, we can decide >> how to partition it into one ore more substates for the new >> KVM_GET/SET_VCPU_STATE interface. >> >> What I read so far (or tried to patch already): >> >> - nmi_masked >> - nmi_pending >> - nmi_injected >> - kvm_queued_exception (whole struct content) >> - KVM_REQ_TRIPLE_FAULT (from vcpu.requests) >> >> Unclear points (for me) from the last discussion: >> >> - sipi_vector >> - MCE (covered via kvm_queued_exception, or does it require more?) >> >> Please extend or correct the list as required. > > hflags. Qemu supports GIF, kvm supports GIF, but no side knows how to > sync it. BTW, GIF is related to svm nesting, right? Orit, are there any additional states arriving on the vmx side as well with your nesting patches? Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux