From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: handle_wrmsr behavior under kvm-83 Date: Mon, 02 Feb 2009 18:27:07 +0200 Message-ID: <49871EDB.7000200@redhat.com> References: <5670163.50721233272892755.JavaMail.root@mailserv1> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm To: Steven Stovall Return-path: Received: from mx2.redhat.com ([66.187.237.31]:37637 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752503AbZBBQ1M (ORCPT ); Mon, 2 Feb 2009 11:27:12 -0500 In-Reply-To: <5670163.50721233272892755.JavaMail.root@mailserv1> Sender: kvm-owner@vger.kernel.org List-ID: Steven Stovall wrote: > When looking at the EXIT_REASON_MSR_WRITE events that trigger handle_wrmsr() invocations, why do I only seem to see indices for MSR_MTRRfix* (0x250 - 0x2ff)? This behavior seems to have changed since kvm-60, where I would see for example SYSENTER MSR writes. > In vmx_init(): vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_FS_BASE); vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_GS_BASE); vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_IA32_SYSENTER_CS); vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_IA32_SYSENTER_ESP); vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_IA32_SYSENTER_EIP); -- error compiling committee.c: too many arguments to function