469811 – Memory analysis should use 'vpid' context instead of 'vtid'

Bug 469811 - Memory analysis should use 'vpid' context instead of 'vtid'

Summary: Memory analysis should use 'vpid' context instead of 'vtid'

Status:	NEW

Alias:	None

Product:	Tracecompass
Classification:	Tools
Component:	LTTng (show other bugs)
Version:	1.0.0
Hardware:	PC Linux

Importance:	P3 normal
Target Milestone:	---
Assignee:	Project Inbox
QA Contact:	Project Inbox

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-06-10 04:42 EDT by Alexandre Montplaisir
Modified:	2016-03-14 10:45 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Video of the vpid vs. vtid problem (3.42 MB, video/ogg) 2015-08-20 22:35 EDT, Alexandre Montplaisir	no flags	Details
View All 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 Alexandre Montplaisir

2015-06-10 04:42:07 EDT

Since a memory allocation affects a whole process, and not just a thread, the UST Memory analysis should track PIDs instead of TIDs. This would mean changing the analysis requirements and state tracking to use 'vpid' instead of 'vtid', which is also available for UST traces.

Comment 1 Alexandre Montplaisir

2015-08-20 22:35:21 EDT

Created attachment 255998 [details]
Video of the vpid vs. vtid problem

Interestingly, if a trace (correctly) has vpid contexts enabled and not vtids, a weird bug happens where two series will be shown on the graph, one called "(-1)" and the other called "Others (-1)".

Here is a video displaying it. This is with current master (without my UstEventLayout branch).

Comment 2 Bernd Hufmann

2016-03-14 10:45:24 EDT

> Interestingly, if a trace (correctly) has vpid contexts enabled and not
> vtids, a weird bug happens where two series will be shown on the graph, one
> called "(-1)" and the other called "Others (-1)".
> 
This part should be fixed with patch https://git.eclipse.org/r/#/c/68312/1