From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Boris Ostrovsky <boris.ostrovsky@amd.com>
Cc: Marcus Granado <Marcus.Granado@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"msw@amazon.com" <msw@amazon.com>,
"andrew.thomas@oracle.com" <andrew.thomas@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"jun.nakajima@intel.com" <jun.nakajima@intel.com>,
"kurt.hackel@oracle.com" <kurt.hackel@oracle.com>,
"jacob.shin@amd.com" <jacob.shin@amd.com>,
Marcus Granado <marcus.granado@citrix.com>,
"Marcos.Matsunaga@oracle.com" <Marcos.Matsunaga@oracle.com>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"Sherry.Hurwitz@amd.com" <Sherry.Hurwitz@amd.com>
Subject: Re: Xen, oprofile, perf, PEBS, event counters, PVHVM, PV
Date: Wed, 16 Jan 2013 11:40:50 -0600 [thread overview]
Message-ID: <1358358050.2964.10.camel@Greyghost-ubuntu> (raw)
In-Reply-To: <50F6D2C7.1020606@amd.com>
On Wed, 2013-01-16 at 11:18 -0500, Boris Ostrovsky wrote:
> On 01/15/2013 11:47 PM, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jan 15, 2013 at 05:11:01PM +0000, Marcus Granado wrote:
> >> On 14/01/13 20:45, Konrad Rzeszutek Wilk wrote:
>
> >>> And it occurs to me it could be possible be to make some inroads on making
> >>> performance monitoring easier:
> >>>
> >>> 1). fix the glaring omissions in oprofile for the new CPUs
> >>> 2). Add a register keyhandle to get some debug info.
> >>> 3). piggyback on oprofile hypercalls and insert some bridge in perf (lots
> >>> of handwaving here). Or perhaps emulate in the Linux kernel the
> >>> wmsrs (so xen_safe_wrmsrs) and have the pvops kernel based on the MSRs
> >>> make the hypercalls to setup the buffers, etc.
> >>>
> >>> 3a). new hypercalls? intercept rdmsr/wrmsrs and stuff the right data
> >>> in the initial domain? Other thoughts?
> >>>
> >>> 4). Extend perf to have '--xen' so it can also look at the xen-hypervisor
> >>> ELF file.
> >>
> >> 5) live event reports from xenoprof/opreport, ala perf top.
> >> 6) ports of oprofile kernel modules for other oses (bsd, windows,
> >> mirage), so that these oses can be used as active participants.
>
> (+ Suravee)
>
> What is the status of oprofile development in general (on Linux)? I
> don't see a whole lot of activity there, it appears to be more in
> maintenance mode.
Linux OProfile driver is in maintenance mode. However, the user-space tools have been converted to use
PERF syscalls interface which allows it to support per-process (non-root) profiling (similar to PERF default mode).
One advantage of OProfile is the large database of performance counters on various platforms.
Suravee
> I realize that doing (4) may end up being a lot of work but given much
> more active perf development it seems to me that this should be the
> preferred route.
> -boris
next prev parent reply other threads:[~2013-01-16 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 20:45 Xen, oprofile, perf, PEBS, event counters, PVHVM, PV Konrad Rzeszutek Wilk
2013-01-15 9:13 ` Jan Beulich
2013-01-15 17:11 ` Marcus Granado
2013-01-16 4:47 ` Konrad Rzeszutek Wilk
2013-01-16 16:18 ` Boris Ostrovsky
2013-01-16 17:40 ` Suravee Suthikulpanit [this message]
2013-01-18 15:43 ` 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=1358358050.2964.10.camel@Greyghost-ubuntu \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=Marcos.Matsunaga@oracle.com \
--cc=Marcus.Granado@eu.citrix.com \
--cc=Sherry.Hurwitz@amd.com \
--cc=andrew.thomas@oracle.com \
--cc=boris.ostrovsky@amd.com \
--cc=jacob.shin@amd.com \
--cc=jun.nakajima@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=marcus.granado@citrix.com \
--cc=msw@amazon.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).