From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: List of unaccessible x86 states Date: Fri, 23 Oct 2009 15:00:23 -0200 Message-ID: <20091023170023.GA5126@amt.cnet> References: <4ADDB49B.3010101@siemens.com> <20091020184514.GA15411@amt.cnet> <4AE1AAC5.1020105@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm-devel , Avi Kivity , Gleb Natapov To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33841 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752873AbZJWTKa (ORCPT ); Fri, 23 Oct 2009 15:10:30 -0400 Content-Disposition: inline In-Reply-To: <4AE1AAC5.1020105@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Oct 23, 2009 at 03:08:21PM +0200, Jan Kiszka wrote: > Marcelo Tosatti wrote: > > On Tue, Oct 20, 2009 at 03:01:15PM +0200, 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?) > > > > Should save/restore the MCE MSRs (its contents are currently > > lost/overwritten AFAICS). > > > > MTRR contents are also dropped. > > Hmm, the code path is winding, but aren't they already available to user > space via GET/SET_MSRS? Yes, nevermind, irrelevant to the current discussion.