From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v1 5/5] KVM: Expose a version 1 architectural PMU to guests Date: Wed, 18 May 2011 14:37:44 +0300 Message-ID: <4DD3AF88.2040704@redhat.com> References: <1305129333-7456-1-git-send-email-avi@redhat.com> <1305129333-7456-6-git-send-email-avi@redhat.com> <20110517194117.GA26184@elte.hu> <4DD38B57.2070904@redhat.com> <20110518110759.GB16556@elte.hu> <1305718350.2466.7110.camel@twins> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Ingo Molnar , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Arnaldo Carvalho de Melo To: Peter Zijlstra Return-path: In-Reply-To: <1305718350.2466.7110.camel@twins> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/18/2011 02:32 PM, Peter Zijlstra wrote: > On Wed, 2011-05-18 at 13:07 +0200, Ingo Molnar wrote: > > > > It does through raw events - which are indeed model specific. > > Which is exactly what is needed anyway, he gets a raw msr value. > > The only thing that is not exposed is the ANY bit, but since KVM doesn't > expose HT anyway that doesn't matter. If I were to use raw events, I'd need to program AMD and Intel hosts separately. As it is, I just use the generic counters and the perf backend does its thing. (note, INV and CMASK are hardly important, I think we can get away without implementing them) -- error compiling committee.c: too many arguments to function