From: Jan Kiszka <jan.kiszka@siemens.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Avi Kivity <avi@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH v1 0/5] KVM in-guest performance monitoring
Date: Thu, 12 May 2011 11:47:51 +0200 [thread overview]
Message-ID: <4DCBACC7.8080000@siemens.com> (raw)
In-Reply-To: <20110512093309.GD8707@8bytes.org>
On 2011-05-12 11:33, Joerg Roedel wrote:
> On Wed, May 11, 2011 at 11:55:28AM -0400, Avi Kivity wrote:
>> This not-for-merging patchset exposes an emulated version 1 architectural
>> performance monitoring unit to KVM guests. The PMU is emulated using
>> perf_events, so the host kernel can multiplex host-wide, host-user, and the
>> guest on available resources.
>>
>> Caveats:
>> - counters that have PMI (interrupt) enabled stop counting after the
>> interrupt is signalled. This is because we need one-shot samples
>> that keep counting, which perf doesn't support yet
>> - some combinations of INV and CMASK are not supported
>> - counters keep on counting in the host as well as the guest
>> - the RDPMC instruction and CR4.PCE bit are not yet emulated
>> - there is likely a bug in the implementation; running 'perf top' in
>> a guest that spends 80% of its time in userspace shows perf itself
>> as consuming almost all cpu
>>
>> perf maintainers: please consider the first three patches for merging (the
>> first two make sense even without the rest). If you're familiar with the Intel
>> PMU, please review patch 5 as well - it effectively undoes all your work
>> of abstracting the PMU into perf_events by unabstracting perf_events into what
>> is hoped is a very similar PMU.
>
> Gaah, I was just about to submit a talk about PMU virtualization for KVM
> Forum :)
>
> Anyway, I thought about a paravirt-approach instead of implementing a
> real PMU... But there are certainly good reasons for both.
Paravirt is taking away the pressure from CPU vendors to do their virt
extensions properly - and doesn't help with unmodifiable OSes.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-12 9:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 15:55 Avi Kivity
2011-05-11 15:55 ` [PATCH v1 1/5] perf: add context parameter to perf_event overflow handler Avi Kivity
2011-06-03 14:41 ` Peter Zijlstra
2011-06-05 8:07 ` Avi Kivity
2011-05-11 15:55 ` [PATCH v1 2/5] x86, perf: add constraints for architectural PMU v1 Avi Kivity
2011-05-11 15:55 ` [PATCH v1 3/5] perf: export perf_event_refresh() to modules Avi Kivity
2011-05-11 15:55 ` [PATCH v1 4/5] KVM: Expose kvm_lapic_local_deliver() Avi Kivity
2011-05-11 15:55 ` [PATCH v1 5/5] KVM: Expose a version 1 architectural PMU to guests Avi Kivity
2011-05-17 19:41 ` Ingo Molnar
2011-05-18 9:03 ` Avi Kivity
2011-05-18 11:07 ` Ingo Molnar
2011-05-18 11:29 ` Peter Zijlstra
2011-05-18 11:57 ` Ingo Molnar
2011-05-18 11:32 ` Peter Zijlstra
2011-05-18 11:37 ` Avi Kivity
2011-05-18 12:35 ` Peter Zijlstra
2011-05-18 12:49 ` Avi Kivity
2011-06-03 14:41 ` Peter Zijlstra
2011-06-05 8:12 ` Avi Kivity
2011-06-03 14:41 ` Peter Zijlstra
2011-06-05 8:12 ` Avi Kivity
2011-05-12 9:33 ` [PATCH v1 0/5] KVM in-guest performance monitoring Joerg Roedel
2011-05-12 9:47 ` Jan Kiszka [this message]
2011-05-12 9:53 ` Avi Kivity
2011-05-12 13:11 ` Joerg Roedel
2011-05-12 13:23 ` Jan Kiszka
2011-05-12 13:43 ` Joerg Roedel
2011-05-12 13:31 ` Avi Kivity
2011-05-12 14:24 ` Joerg Roedel
2011-05-12 14:37 ` Avi Kivity
2011-05-12 14:45 ` Avi Kivity
2011-05-13 12:34 ` Joerg Roedel
2011-05-12 9:51 ` Avi Kivity
2011-05-12 13:06 ` Joerg Roedel
2011-05-12 13:38 ` Avi Kivity
2011-05-12 14:29 ` Joerg Roedel
2011-05-17 9:52 ` Avi Kivity
2011-06-01 9:45 ` Avi Kivity
2011-06-01 10:26 ` Peter Zijlstra
2011-06-01 11:26 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DCBACC7.8080000@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=avi@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome