Bug 518781 - deduce flamegraph pid/tid/procname data from kernel scheduler tracepoints
Summary: deduce flamegraph pid/tid/procname data from kernel scheduler tracepoints
Status: UNCONFIRMED
Alias: None
Product: Tracecompass
Classification: Tools
Component: LTTng (show other bugs)
Version: 2.3.0   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-26 09:17 EDT by Milian Wolff CLA
Modified: 2017-07-03 10:31 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Milian Wolff CLA 2017-06-26 09:17:41 EDT 
The UST flamegraph depends on context data, cf.: http://archive.eclipse.org/tracecompass/doc/stable/org.eclipse.tracecompass.doc.user/LTTng-UST-Analyses.html

When profiling kernel and UST, this data could instead be deduced from the scheduler tracepoints, reducing the data size for the UST events.
Comment 1 Genevieve Bastien CLA 2017-07-03 10:27:12 EDT 
Hi Millian,

Thanks for reporting this. Work is in progress in the tracecompass incubator project for more generic and flexible callstack/flamegraphs. Patches are currently on gerrit and waiting review
Comment 2 Genevieve Bastien CLA 2017-07-03 10:31:02 EDT 
oops, it submitted before I finished the message...

You could try running tracecompass and the incubator from the source code (instructions are here https://wiki.eclipse.org/Trace_Compass/Development_Environment_Setup )

Otherwise, the incubator is currently waiting for initial review before we can make builds from it and deploy them in an update site. When that is done, you'll be able to install the new features from any Trace Compass 3.0+

I'll keep you posted on the updates.