All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 6 Apr 2011 11:31:31 -0500	[thread overview]
Message-ID: <20110406163130.GA2360@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

Thanks, Anil. I was able to get your patch to work. If anyone is
interested in what I did, please see:

	https://bugzilla.redhat.com/show_bug.cgi?id=693596#c2

An a related note, would there be any interest in cleaning up this patch
and moving it to 2.6.38 as a part of Google Summer of Code?

-- 
Mike

:wq

  reply	other threads:[~2011-04-06 16:31 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 [this message]
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=20110406163130.GA2360@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.