From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: MSRs load/store Date: Mon, 07 Dec 2009 17:11:57 +0200 Message-ID: <4B1D1B3D.6060305@redhat.com> References: <6d8082040912070707g3d809d2fy9319d01609133083@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Jiaqing Du Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38516 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935211AbZLGPLy (ORCPT ); Mon, 7 Dec 2009 10:11:54 -0500 In-Reply-To: <6d8082040912070707g3d809d2fy9319d01609133083@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/07/2009 05:07 PM, Jiaqing Du wrote: > Hi List, > > My question is about VM-Exit& VM-Entry controls for MSRs on Intel's processors. > > For VM-Exit, a VMM can specify lists of MSRs to be stored and loaded > on VM exits. But for VM-Entry, a VMM can only specify a list of MSRs > to be loaded on VM entries. Why does not the processor have the > feature that stores MSRs before loading new ones for VM entries? > Presumably the host knows what values are in those MSRs, so it doesn't need to store them. -- error compiling committee.c: too many arguments to function