From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "W. Michael Petullo" <mike@flyn.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: OProfile patch for Linux 3.0
Date: Tue, 13 Sep 2011 22:17:44 -0700 [thread overview]
Message-ID: <4E7038F8.309@goop.org> (raw)
In-Reply-To: <20110914023052.GA9816@imp.local>
On 09/13/2011 07:30 PM, W. Michael Petullo wrote:
> I have ported Anil's passive profile-capable OProfile patch to Linux
> 3.0. Please see:
>
> http://www.flyn.org/patches/linux-xen-passive-oprofile/linux-3.0-xen-passive-oprofile.patch.gz
>
> With this patch applied to Linux 3.0, I can perform passive
> profiling of an unprivileged Xen domain.
>
Unfortunately this patch is unusable in the current form, so every now
and again someone reports it to a current kernel, but its ends up being
as useful as kicking a dead whale down the beach.
I don't suppose you have any inclination to actually pick it apart and
turn it into a useful series of functionally distinct patches so we can
consider upstreaming it? (I guess you could consider that to be
dynamiting the whale, but at that point the analogy completely comes
apart in gory chunks.)
Thanks,
J
next prev parent reply other threads:[~2011-09-14 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 2:30 OProfile patch for Linux 3.0 W. Michael Petullo
2011-09-14 5:17 ` Jeremy Fitzhardinge [this message]
2011-09-14 9:00 ` 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=4E7038F8.309@goop.org \
--to=jeremy@goop.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 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.