xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: "W. Michael Petullo" <mike@flyn.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: OProfile patch for Linux 3.2
Date: Fri, 17 Feb 2012 12:44:11 -0400	[thread overview]
Message-ID: <20120217164410.GA14012@andromeda.dapyr.net> (raw)
In-Reply-To: <20120201012811.GA1994@imp.flyn.org>

On Tue, Jan 31, 2012 at 07:28:12PM -0600, W. Michael Petullo wrote:
> >> I have ported Anil's passive profile-capable OProfile patch to Linux
> >> 3.2. I have be able to hobble this patch along to new kernel versions, but
> >> it is in need of additional work if it is to be submitted upstream. Please
> >> see:
> >> 
> >> http://www.flyn.org/patches/linux-xen-passive-oprofile/linux-3.2-xen-passive-oprofile.patch.gz
> >> 
> >> With this patch applied to Linux 3.2, I can perform passive
> >> profiling of an unprivileged Xen domain.
> 
> > What version of oprofile did you use?
> 
> Fedora's oprofile-0.9.6-21.fc16.x86_64.

So I took a spin at this - it applies nicely and cleanly to 3.2, and
was wondering how you profile passive domains?

I do something like this:

opcontrol --vmlinux=/mnt/lab/vmlinux-dom0 --xen=/mnt/lab/xen-syms --passive-domains=3,2 --callgraph=10 --passive-images=/mnt/lab/10gb/tiny-vmlinux  -p=cpu 
opcontrol --start-daemon

opcontrol --start
/mnt/lab/10gb/create_csv.sh 1
opcontrol --stop

The little create_csv.sh makes the two domains talk to each other
(netperf) and I want to get a feel for what it is happening.

But what I get is exclusivly to domain0 and to xen. Nothing about
the guests?

Are you doing something speciail to profile the passive domains?

Thanks.

      reply	other threads:[~2012-02-17 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 23:54 OProfile patch for Linux 3.2 W. Michael Petullo
2012-02-01  1:05 ` Konrad Rzeszutek Wilk
2012-02-01  1:28   ` W. Michael Petullo
2012-02-17 16:44     ` Konrad Rzeszutek Wilk [this message]

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=20120217164410.GA14012@andromeda.dapyr.net \
    --to=konrad@darnok.org \
    --cc=mike@flyn.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).