From: Keir Fraser <keir.xen@gmail.com>
To: Ruslan Nikolaev <nruslan_devel@yahoo.com>, xen-devel@lists.xensource.com
Subject: Re: Perfctr-Xen framework for permonace analysis
Date: Thu, 12 May 2011 21:09:23 +0100 [thread overview]
Message-ID: <C9F1FD03.1A371%keir.xen@gmail.com> (raw)
In-Reply-To: <395284.39970.qm@web113610.mail.gq1.yahoo.com>
On 12/05/2011 20:36, "Ruslan Nikolaev" <nruslan_devel@yahoo.com> wrote:
> Hi
>
> I want to make an announcement about new perfomance monitoring framework.
>
> Perfctr-Xen framework that enables per-thread performance analysis in Xen.
> Current version is capable of properly virtualizing counters in both
> paravirtualized and HVM modes. It is based on perfctr (which is a library and
> kernel module for non-virtualized guests), ported to Xen, and extended to work
> properly in virtualized environment. Both accumulative and interrupt modes
> counting (profiling) are supported.
>
> The advantage of Perfctr-Xen is that it does not require specific HVM
> extensions which are needed for vpmu driver, can work in paravirtualized mode,
> and it also quite universal: works with many common tools such as PAPI,
> HPCToolkit, TAU PerfExplorer. It supports proper per-domain and per-thread
> virtualization. It is light-weight, supports wide range of CPUs, does not
> require save-and-restore for accumulative mode of counting (it uses counter
> offsetting), avoids expensive hypercalls and counter re-programming in certain
> circumstances (when threads are counting the same type of events). In
> addition, some techniques are employed to account for the overhead caused by
> the framework itself. This makes measurements quite accurate.
>
> Perfctr-Xen consists of series of patches that need to be applied to Xen,
> Linux, perfctr. There are available at:
> http://people.cs.vt.edu/~rnikola/
>
> The code is available under LGPL. It would be great to discuss if and how it
> can be integrated into Xen.
Could it reasonably replace the oprofile stuff we have already? I wouldn't
want yet another perfctr subsystem/interface unless it supplants an existing
one. We need a revolving door policy here I think.
-- Keir
> The publication regarding Perfctr-Xen is at:
> http://portal.acm.org/citation.cfm?id=1952687
>
> Thanks,
> Ruslan Nikolaev
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-12 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 19:36 Perfctr-Xen framework for permonace analysis Ruslan Nikolaev
2011-05-12 20:09 ` Keir Fraser [this message]
2011-05-12 20:35 ` Ruslan Nikolaev
2011-05-13 13:57 ` George Dunlap
2011-05-13 13:59 ` George Dunlap
2011-05-13 23:03 ` Ruslan Nikolaev
2011-05-16 20:44 ` Ruslan Nikolaev
2011-08-15 15:21 ` Konrad Rzeszutek Wilk
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=C9F1FD03.1A371%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=nruslan_devel@yahoo.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).