From: "W. Michael Petullo" <mike@flyn.org>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Questions about OProfile
Date: Tue, 5 Apr 2011 16:45:39 -0500 [thread overview]
Message-ID: <20110405214539.GA1970@imp.local> (raw)
In-Reply-To: <CEE47386-BE4D-4683-8C60-0153124C683F@recoil.org>
>> First, what is the status of Xenoprof? The latest patch is against 0.9.5,
>> but OProfile 0.9.6 is about 16 months old. Is Xenoprof actively
>> maintained?
> There is a crufty pv_ops patch that I forward ported to 2.6.32 in this tree:
>
> https://github.com/avsm/linux-2.6.32-xen-oprofile
So, is it true that I need to 1) use this patch or 2) use a non-PV
Ops Dom0? I thought 2.6.32 was already non-PV Ops.
> It's not suitable for upstreaming, but passive profiling of domains
> works fine for me using this kernel. Ian Pratt suggested dropping
> active profiling in order to simplify the patch: does anyone actually
> use active profiling?
I am especially interested in passive profiling because I wish to profile
experimental kernels. Developing on top of Xen is a big win for this type
of work precisely because of tools like gdbsx and passive profiling. With
this capability, there is no need to spend time adding debugging or
profiling features into a new kernel.
> Jeremy also pointed out the new perf framework in Linux to me at the
> hackathon, but I haven't had a chance to look at how it works:
>
> https://perf.wiki.kernel.org/index.php/Main_Page
--
Mike
:wq
next prev parent reply other threads:[~2011-04-05 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 17:03 Questions about OProfile W. Michael Petullo
2011-04-05 17:49 ` Anil Madhavapeddy
2011-04-05 21:45 ` W. Michael Petullo [this message]
2011-04-05 21:53 ` Anil Madhavapeddy
2011-04-06 16:31 ` W. Michael Petullo
2011-04-11 14:22 ` Konrad Rzeszutek Wilk
2011-04-18 18:33 ` W. Michael Petullo
2011-04-18 20:10 ` 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=20110405214539.GA1970@imp.local \
--to=mike@flyn.org \
--cc=anil@recoil.org \
--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).