From: Robert Richter <robert.richter@amd.com>
To: Carl Love <cel@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, oprofile-list@lists.sourceforge.net,
cel <cel@linux.vnet.ibm.com>,
cbe-oss-dev <cbe-oss-dev@ozlabs.org>
Subject: Re: [Patch 0/3] Overview, OProfile SPU event profiling support for IBM Cell processor
Date: Thu, 8 Jan 2009 16:48:35 +0100 [thread overview]
Message-ID: <20090108154835.GQ15411@erda.amd.com> (raw)
In-Reply-To: <1228177106.6509.285.camel@carll-linux-desktop>
On 01.12.08 16:18:26, Carl Love wrote:
> This is a rework of the previously posted set of patches.
>
> Patch 1 is the user level patch to add the SPU events to the user
> OProfile tool.
>
> Patch 2 is a kernel patch to do code clean up and restructuring to make
> it easier to add the new SPU event profiling support. This patch makes
> no functional changes.
>
> Patch 3 is a kernel patch to add the SPU event profiling support.
I applied patch 2 & 3 to:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git cell
The patches did not apply cleanly. I had to change the path to
arch/powerpc/include/asm/, fix cell/pr_util.h and did some whitespace
cleanups. Please run your tests on the cell branch.
Thanks,
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2009-01-08 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 0:18 [Patch 0/3] Overview, OProfile SPU event profiling support for IBM Cell processor Carl Love
2009-01-08 15:48 ` Robert Richter [this message]
2009-01-09 0:26 ` Carl Love
2009-01-09 14:30 ` Robert Richter
2009-01-10 23:31 ` Benjamin Herrenschmidt
2009-01-12 16:15 ` Carl Love
2009-01-12 17:52 ` Robert Richter
2009-01-12 17:59 ` Arnd Bergmann
2009-01-12 18:10 ` Carl Love
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=20090108154835.GQ15411@erda.amd.com \
--to=robert.richter@amd.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=cel@linux.vnet.ibm.com \
--cc=cel@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oprofile-list@lists.sourceforge.net \
/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