Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] [EXTERNAL]Re: Trace Server source code location

Hi,


Thapi is only one type of GPU traces. There is a project to handle multiple sources of GPU CTF traces which are much more specific than generic CTF traces.


Since CTF is a pretty generic format, most analysis only work for a specific type.

Analyses can be written using EASE scripting, XML analyses, or creating a new Eclipse bundle as described by Bernd.


Regards,
Arnaud


On 2024-05-06 9:41 a.m., Matthew Khouzam via tracecompass-dev wrote:
There is a new project called Thapi, @Arnaud Fiorini, do you think this could help? This could maybe save some work on both sides?
From: tracecompass-dev <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Bernd Hufmann via tracecompass-dev <tracecompass-dev@xxxxxxxxxxx>
Sent: Friday, May 3, 2024 11:20 AM
To: tracecompass-dev@xxxxxxxxxxx <tracecompass-dev@xxxxxxxxxxx>
Cc: Bernd Hufmann <bernd.hufmann@xxxxxxxxxxxx>
Subject: Re: [tracecompass-dev] [EXTERNAL]Re: Trace Server source code location
 
Hi,

First of all, Trace Compass has support for generic CTF traces. With that you would be able to see the raw trace in the events table plus have the Histogram view as well. 

Secondly, to add some specific trace parsing logic and to have custom views for your trace type (implemented in data providers) similar to LTTng-UST then it's a good approach to create a custom Eclipse bundle. Since you plan to use it with the trace server, make sure that it doesn't contain any UI code and dependencies (like LTTng-UST core bundle).

Thirdly, you will have to package the new Eclipse bundle with the trace server. For that you can have a custom traceserver product defined. You can copy the  org.eclipse.tracecompass.incubator.trace.server.product and modify content accordingly.

Regards
Bernd
From: tracecompass-dev <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Greg Savin via tracecompass-dev <tracecompass-dev@xxxxxxxxxxx>
Sent: April 29, 2024 7:07 PM
To: tracecompass-dev@xxxxxxxxxxx <tracecompass-dev@xxxxxxxxxxx>
Cc: Greg Savin <gsavin@xxxxxxxx>
Subject: Re: [tracecompass-dev] [EXTERNAL]Re: Trace Server source code location
 
Thanks.  To the trace server, if I want to add support for a CTF-format trace that is different from the schema of LTTNG-UST traces and uses a different tracing agent (barectf), is a reasonable approach to create a new Eclipse bundle that is generally patterned after org.eclipse.tracecompass/lttng/org.eclipse.tracecompass.lttng2.ust.core, but with the appropriate differences accounted for?

Regards,
Greg
From: Bernd Hufmann <bernd.hufmann@xxxxxxxxxxxx>
Sent: Friday, April 26, 2024 6:56 PM
To: tracecompass-dev@xxxxxxxxxxx <tracecompass-dev@xxxxxxxxxxx>
Cc: Greg Savin <gsavin@xxxxxxxx>
Subject: [EXTERNAL]Re: Trace Server source code location
 
Hi,

yes, that's the location. 

Regards,
Bernd
From: tracecompass-dev <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Greg Savin via tracecompass-dev <tracecompass-dev@xxxxxxxxxxx>
Sent: April 26, 2024 5:07 PM
To: tracecompass-dev@xxxxxxxxxxx <tracecompass-dev@xxxxxxxxxxx>
Cc: Greg Savin <gsavin@xxxxxxxx>
Subject: [tracecompass-dev] Trace Server source code location
 
Hi all,

Is it still true that the repository at https://github.com/eclipse-tracecompass-incubator/org.eclipse.tracecompass.incubator.git is the place where the latest Trace Server source code lives?

Regards,
Greg S.

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tracecompass-dev

Back to the top