From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: perf uncore & lkvm woes Date: Thu, 16 Aug 2012 13:17:26 +0200 Message-ID: <1345115846.29668.16.camel@twins> References: <1345101585.31459.112.camel@twins> <502CA368.8050404@linux.intel.com> <502CB1F6.4010204@redhat.com> <502CD444.5020807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: Pekka Enberg , "Yan, Zheng" , Sasha Levin , Asias He , Cyrill Gorcunov , Ingo Molnar , KVM General , Gleb Natapov To: Avi Kivity Return-path: Received: from merlin.infradead.org ([205.233.59.134]:54194 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751413Ab2HPLRl convert rfc822-to-8bit (ORCPT ); Thu, 16 Aug 2012 07:17:41 -0400 In-Reply-To: <502CD444.5020807@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2012-08-16 at 14:06 +0300, Avi Kivity wrote: > Another option is to deal with them on the host side. That has the > benefit of working with non-Linux guests too. Right, its an insane amount of MSRs though, but it could be done if someone takes the time to enumerate them all. If KVM then simply ignores all writes and returns all 0 on read we can do the same we do for the regular PMU in check_hw_exists(). > We can just ignore the MSR and print some warning. If you don't mind printing a warning every time a Linux guest boots ;-)