public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
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] OProfile SPU event profiling support for IBM Cell processor
Date: Tue, 25 Nov 2008 17:00:30 +0100	[thread overview]
Message-ID: <200811251700.30926.arnd@arndb.de> (raw)
In-Reply-To: <1227568781.6509.198.camel@carll-linux-desktop>

On Tuesday 25 November 2008, Carl Love wrote:
> This patch set consists of two kernel patches and one user level patch
> to add SPU event based profiling support to OProfile for the IBM Cell
> processor.  The first patch in the series is the user level patch that
> adds the needed events and event checking to the user tool.  The second
> patch is the first of two kernel patches.  It makes some structural
> changes to the kernel code to make it easier to add the specific
> functions for doing SPU event profiling.  The first kernel patch does
> not make any functional changes.  The third patch in the series is the
> second kernel patch where the actual SPU event profiling code support is
> added to the kernel.

Thanks for your submission!

I can't comment on the oprofile user code, but I have some comments
on the implementation in the third patch.

Are the patches interdependent, or will old versions of the oprofile
tool work with new kernels and vice versa?

	Arnd <><

  reply	other threads:[~2008-11-25 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 23:19 [Patch 0/3] OProfile SPU event profiling support for IBM Cell processor Carl Love
2008-11-25 16:00 ` Arnd Bergmann [this message]
2008-11-25 19:07   ` 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=200811251700.30926.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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