From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Lv, Hui" <hui.lv@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: About the oprofile tools and related profiling tools
Date: Tue, 31 May 2011 10:35:42 -0400 [thread overview]
Message-ID: <20110531143542.GK14641@dumpdata.com> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F233F62EA4E@shsmsx502.ccr.corp.intel.com>
On Mon, May 30, 2011 at 11:25:10AM +0800, Lv, Hui wrote:
> Hi, list
>
> I found the oprofile tools were not supported in PVOPS domain0(from jeremy's tree). Someone has made the patch to enable it. When I applied such patch, xenoprofile can work. But the results were not trusted. (I think, part of this reason was due to xen, which changed the NMI handling way, but did not update the xenoprofile part)
Hm, I don't think the Jeremy's tree had support for it.
Mike Petullo wrote a patch for the oprofile support and Xen for 2.6.39 kernels.
If you want to try it out, I would suggest you play with devel/next-2.6.39 in my
git tree git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git.
> So my question is that, does anyone still maintain this tools? Or, do xen guys have a plan to enable more powerful profiling tools like 'perf' in native Linux or something else.
Would love to, except that I don't think anybody has signed up for that yet.
> One of my basic feeling about xen's performance profiling tools is that the functional level profiling tools like oprofile were neglected recently.
>
> Best regards!
> Lv,hui
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-31 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 3:25 About the oprofile tools and related profiling tools Lv, Hui
2011-05-31 9:44 ` George Dunlap
2011-05-31 14:35 ` Konrad Rzeszutek Wilk [this message]
2011-05-31 15:42 ` Lv, Hui
2011-05-31 16:02 ` Konrad Rzeszutek Wilk
2011-05-31 16:21 ` W. Michael Petullo
2011-06-01 0:16 ` Lv, Hui
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=20110531143542.GK14641@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=hui.lv@intel.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).