[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45C4EA7D.4000709@us.ibm.com>
Date: Sat, 03 Feb 2007 14:03:09 -0600
From: Maynard Johnson <maynardj@...ibm.com>
To: Arnd Bergmann <arnd@...db.de>
CC: cbe-oss-dev@...abs.org, linuxppc-dev@...abs.org,
oprofile-list@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [Cbe-oss-dev] [RFC, PATCH 4/4] Add support to OProfile for profiling
Cell BE SPUs -- update
Arnd Bergmann wrote:
>On Friday 02 February 2007 17:47, Maynard Johnson wrote:
>
>
>>>We also want to be able to profile the context switch code itself, which
>>>means that we also need one event buffer associated with the kernel to
>>>collect events that for a zero context_id.
>>>
>>>
>>The hardware design precludes tracing both SPU and PPU simultaneously.
>>
>>
>>
>I mean the SPU-side part of the context switch code, which you can find
>in arch/powerpc/platforms/cell/spufs/spu_{save,restore}*.
>
>This code is the one that runs when context_id == 0 is passed to the
>callback.
>
>
I presume you mean 'object_id'. What you're asking for is a new
requirement, and one which I don't believe is achievable in the current
timeframe. Since this is spufs code that's dynamicaly loaded into the
SPU at runtime, the symbol information for this code is not accessible
to the userspace post-processing tools. It would require an altogether
different mechanism to record samples along with necessary information,
not to mention the changes required in the post-processing tools. This
will have to be a future enhancement.
-Maynard
> Arnd <><
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists