All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Carl Love <cel@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, cel <cel@linux.vnet.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	oprofile-list@lists.sourceforge.net,
	cbe-oss-dev <cbe-oss-dev@ozlabs.org>
Subject: Re: [Cbe-oss-dev] [Patch 1/3] User OProfile support for the IBM CELL processor SPU	event profiling
Date: Tue, 02 Dec 2008 12:02:13 +1100	[thread overview]
Message-ID: <1228179733.8004.45.camel@localhost> (raw)
In-Reply-To: <1228177110.6509.286.camel@carll-linux-desktop>

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

On Mon, 2008-12-01 at 16:18 -0800, Carl Love wrote:
> This patch adds the SPU event profiling support for the IBM Cell
> processor to the list of available events. The opcontrol script
> patches include a test to see if there is a new cell specific file
> in the kernel oprofile file system.  If the file exists, then the
> kernel supports SPU event profiling.  
> 
> Signed-off-by: Carl Love <carll@us.ibm.com>
> 

> Index: oprofile-cvs/doc/oprofile.xml
> ===================================================================
> --- oprofile-cvs.orig/doc/oprofile.xml
> +++ oprofile-cvs/doc/oprofile.xml
> @@ -123,6 +123,10 @@ For information on how to use OProfile's
>                         of 2.6.22 or more recent.  Additionally, full support of SPE profiling requires a BFD library
>                         from binutils code dated January 2007 or later.  To ensure the proper BFD support exists, run
>                         the <code>configure</code> utility with <code>--with-target=cell-be</code>.
> +
> +		       Profiling the Cell Broadband Engine using SPU events requires a kernel version of 2.6.TBD or
                                                                                                               ^^^

Not sure if you missed that, or it's still TBD, but careful it doesn't
get merged like that.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
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: [Cbe-oss-dev] [Patch 1/3] User OProfile support for the IBM CELL processor SPU	event profiling
Date: Tue, 02 Dec 2008 12:02:13 +1100	[thread overview]
Message-ID: <1228179733.8004.45.camel@localhost> (raw)
In-Reply-To: <1228177110.6509.286.camel@carll-linux-desktop>

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

On Mon, 2008-12-01 at 16:18 -0800, Carl Love wrote:
> This patch adds the SPU event profiling support for the IBM Cell
> processor to the list of available events. The opcontrol script
> patches include a test to see if there is a new cell specific file
> in the kernel oprofile file system.  If the file exists, then the
> kernel supports SPU event profiling.  
> 
> Signed-off-by: Carl Love <carll@us.ibm.com>
> 

> Index: oprofile-cvs/doc/oprofile.xml
> ===================================================================
> --- oprofile-cvs.orig/doc/oprofile.xml
> +++ oprofile-cvs/doc/oprofile.xml
> @@ -123,6 +123,10 @@ For information on how to use OProfile's
>                         of 2.6.22 or more recent.  Additionally, full support of SPE profiling requires a BFD library
>                         from binutils code dated January 2007 or later.  To ensure the proper BFD support exists, run
>                         the <code>configure</code> utility with <code>--with-target=cell-be</code>.
> +
> +		       Profiling the Cell Broadband Engine using SPU events requires a kernel version of 2.6.TBD or
                                                                                                               ^^^

Not sure if you missed that, or it's still TBD, but careful it doesn't
get merged like that.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-02  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  0:18 [Patch 1/3] User OProfile support for the IBM CELL processor SPU event profiling Carl Love
2008-12-02  1:02 ` Michael Ellerman [this message]
2008-12-02  1:02   ` [Cbe-oss-dev] " Michael Ellerman
2008-12-02 15:57   ` Carl Love
2008-12-02 15:57     ` 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=1228179733.8004.45.camel@localhost \
    --to=michael@ellerman.id.au \
    --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 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.