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: Mon, 18 Apr 2011 13:33:59 -0500 [thread overview]
Message-ID: <20110418183359.GA2124@imp.local> (raw)
In-Reply-To: <9D285665-6460-4403-8873-88593CFA5A2D@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.
> I don't understand the question. The above tree is a pv_ops kernel,
> with additional patches applied so it can be a full Xen dom0 (including
> netback, etc). I'm only sporadically updating it as I need to, so you
> probably just want the oprofile patch [1] if you want to apply it to
> some other kernel.
>
> https://github.com/avsm/linux-2.6.32-xen-oprofile/commit/4df4780e638d14249b7aa4005511218a9183c324
I ported Anil's patch to Linux 2.6.38. The result is available at:
http://www.flyn.org/patches/linux-2.6.38-xen-passive-oprofile/linux-2.6.38-xen-passive-oprofile.patch.gz
With this patch applied to Linux 2.6.38 (along with various orthagonal Xen
patches), I can perform passive profiling on an unprivileged Xen domain.
--
Mike
:wq
next prev parent reply other threads:[~2011-04-18 18:33 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
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 [this message]
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=20110418183359.GA2124@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).