Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] ftrace support and roadmap

On 2014-10-21 05:42 AM, Jerome CORRENOZ wrote:
Hi Alexandre,

By "support of ftrace", I mean being able to manage "ftrace" trace format as currently supported fort LTTng trace format.

Please find here link to ftrace documentation: (trace-cmd is a front-end for ftrace)

IMHO Trace Compass could bring useful features compared to KernelShark. At least, it would allow to benefit from the various views provided by Trace Compass to navigate and analyze the trace. And it could also be extended, correlated and integrated with other views (e.g. statistics, performance,...) which can be coming from Trace Compass or specific to a company.

Interesting! I agree, one of the strengths of a unified tool like Trace Compass is that you can reuse all the existing features whenever you add support for a new trace or log format, instead of having to do it from scratch every time.

As Bernd mentioned, we did not have plans to work on this in the short-term. But I could definitely see this as a summer student project (like the pcap parser was). Unless of course someone steps forward to do it before that.

On a related note, I've created a page at . It is just a stub for now, there are many "current" features missing, but it could be useful to track what is planned and what is in the backlog. I'll try to populate it a bit more in the next days.



-----Original Message-----
From: Alexandre Montplaisir [mailto:alexmonthy@xxxxxxxxxxxx]
Sent: Monday, October 20, 2014 10:01 PM
To: tracecompass developer discussions; Jerome CORRENOZ
Subject: Re: [tracecompass-dev] ftrace support and roadmap

Hi Jerome,

Quick question, what do you actually mean by "support for ftrace"?

I have not used ftrace much myself, but I have seen demos of the KernelShark  tool. From a quick look it seems like something that could be easily re-implemented within Trace Compass, possibly using the shiny new data-driven time graph views.

Basically what would be required is:
- A parser for the traces (the "trace-cmd.dat" man page defines that format, right?)
- A mapping from events to states (which events cause which states, under which conditions, etc.)
- A mapping from states to colors to put in the view

Also, just like the Wireshark/pcap parser that was added last summer, the goal wouldn't be to take over or replace Wireshark/KernelShark. But rather, having at least the main features and similar views available in Trace Compass would allow looking at those traces side-by-side with other traces of other types (like other layers in the stack). Which would allow for more advanced use cases.

Would it be something useful, or did you have something else in mind?


On 10/20/2014 06:31 AM, Jerome CORRENOZ wrote:
Hi all,

In our team, we're interested by Trace Compass project which seems promising.

Is it planned to add the support of ftrace which is the tracing framework for the Linux kernel?

More generally, could you please let me know where to get some plans and roadmaps if already available ?

Best regards,

Back to the top