From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Stovall Subject: Re: handle_wrmsr behavior under kvm-83 Date: Mon, 2 Feb 2009 19:06:09 -0800 (PST) Message-ID: <29519922.54891233630369937.JavaMail.root@mailserv1> References: <11756619.54871233630086637.JavaMail.root@mailserv1> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from mail.neuraliq.com ([12.129.246.136]:58423 "EHLO mail.neuraliq.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751221AbZBCDIz (ORCPT ); Mon, 2 Feb 2009 22:08:55 -0500 Received: from localhost (localhost.neuraliq.com [127.0.0.1]) by mail.neuraliq.com (Postfix) with ESMTP id 2F55E267011C for ; Mon, 2 Feb 2009 19:06:25 -0800 (PST) Received: from mail.neuraliq.com ([127.0.0.1]) by localhost (mail.neuraliq.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbsPDTO-0POs for ; Mon, 2 Feb 2009 19:06:10 -0800 (PST) Received: from mail.neuraliq.com (mail.neuraliq.com [12.129.246.135]) by mail.neuraliq.com (Postfix) with ESMTP id 084342670119 for ; Mon, 2 Feb 2009 19:06:10 -0800 (PST) In-Reply-To: <11756619.54871233630086637.JavaMail.root@mailserv1> Sender: kvm-owner@vger.kernel.org List-ID: Well the bits for the sysenter msrs (0x174 - 0x176) are definitely set -- but I still only see exits for 0x200 - 0x2ff. And I definitely wrmsr(l)(MSR_IA32_SYSENTER_*) at vmx_vcpu_setup() time. Ive been going over Ch. 20, and still cant figure out what could be going on here. Steven >Right, but I've tried commenting those calls out, even disabling CPU_BASED_USE_MSR_BITMAPS, allocation >of vmx_msr_bitmap and so on -- without effect. Ive started trying to interrogate the (now-reinstituted) >vmx_msr_bitmap from vmx_vcpu_setup, since the controls can be rewritten there... >Steven ----- Original Message ----- From: "Avi Kivity" To: "Steven Stovall" Cc: "kvm" Sent: Monday, February 2, 2009 8:27:07 AM GMT -08:00 US/Canada Pacific Subject: Re: handle_wrmsr behavior under kvm-83 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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html