|
|
| Re: Embedded multi-thread and multi-processor C profiling [message #128459 is a reply to message #128186] |
Mon, 14 April 2008 15:41   |
Eclipse User |
|
|
|
Originally posted by: kate.kneebone.arm.com
Asaf Yaffe wrote:
>> 2. What assumptions does the thread profiling make about the target's
>> threading model? How easy would it be to add a new threading model?
>
> Can you clarify the question? What do you mean by "threading model"? Can
> you give an example?
Hi,
Anthony's asked me to have a go at clarifying our question (I asked it
of him in the first place).
What we'd like to do is build tools to profile applications which aren't
written in Java (they're written in C in this case) running on top of a
custom threading library, and would very much like to avoid reinventing
too many wheels. TPTP seems like a good place for us to build on top
of, but we're not sure at what level to start building.
Apologies if this is a well documented process, I'm still wading through
lots of documentation. Pointers as to which M to RTFM would be as
useful as direct answers!
Thanks,
Kate
|
|
|
| Re: Embedded multi-thread and multi-processor C profiling [message #128698 is a reply to message #128459] |
Mon, 21 April 2008 07:45 |
 Asaf Yaffe
Messages: 333
Registered: July 2009 |
Senior Member |
|
|
Kate,
Thanks for the clarifications.
>
> What we'd like to do is build tools to profile applications which aren't
> written in Java (they're written in C in this case) running on top of a
> custom threading library, and would very much like to avoid reinventing
> too many wheels. TPTP seems like a good place for us to build on top
> of, but we're not sure at what level to start building.
>
> Apologies if this is a well documented process, I'm still wading through
> lots of documentation. Pointers as to which M to RTFM would be as
> useful as direct answers!
The TPTP documentation for "adopters" (i.e. developers building software
using the TPTP framework) is indeed vague on not well organized. The
TPTP web site contains some high-level documents that describe the
architecture (see here:
http://www.eclipse.org/tptp/home/documents/committers.php,
http://www.eclipse.org/tptp/platform/documents/index.php)
Currently, TPTP provides profilers (or data collectors) only for Java.
Therefore, it seems that what you need is to develop your own "thread
data collector" for C/C++. Such collectors communicate with the rest of
the TPTP framework through the Agent Controller. You should probably
concentrate your effort on learning how to write a TPTP data collector
agent with the Agent Controller SDK (can be downloaded from the TPTP web
site).
I would also suggest to take a closer look at the existing Java Thread
Profiler (in
org.eclipse.tptp.platform.jvmti.runtime\src-native\src\Threa dProf) to
learn what types of events are collected and how they are sent to the
Agent Controller (in src-native\src\jpiagent). You may find that much of
the functionality in JPIAgent for formatting the XML data stream can be
reused.
Also, there is a detailed design document for the Thread Profiler here:
http://www.eclipse.org/tptp/groups/Architecture/documents/fe atures/hf_200320.html
Hope this helps. If you have any specific questions, let us know.
Regards,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
|
|
|
|
Powered by
FUDForum. Page generated in 0.03710 seconds
] 
Search
Help
Register
Login
Home
