linux-kernel - Re: [PATCH v1 5/5] KVM: Expose a version 1 architectural PMU to guests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DD3C03F.4070002@redhat.com>
Date:	Wed, 18 May 2011 15:49:03 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [PATCH v1 5/5] KVM: Expose a version 1 architectural PMU to guests

On 05/18/2011 03:35 PM, Peter Zijlstra wrote:
> On Wed, 2011-05-18 at 14:37 +0300, Avi Kivity wrote:
> >  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.
>
> But why exactly, from what I understood you emulate an actual hardware
> PMU, that means the guest will be writing proper content to the relevant
> MSRs, you can feed that directly into the raw config field (with
> exception of the USR/OS/INT bits).

I am emulating an architectural PMU on a machine that may not have one 
(Intel P4 or AMD), so I need translation between the different config 
formats and event codes.

> I'm fairly sure that emulating the intel arch bits on an cpu that
> otherwise identifies itself as AMD is going to confuse things.

First, we can cheat and identify as Intel.  Second, I'd like to change 
architectural PMU probing to ignore the vendor (pending confirmation 
from AMD that they won't implement cpuid leaf 0xa in a way that is 
incompatible with Intel).  That's what architectural means, no?

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/