Bug 551265 - critical path: Wakeup within the context of IRQ not linked with source
Summary: critical path: Wakeup within the context of IRQ not linked with source
Status: NEW
Alias: None
Product: Tracecompass
Classification: Tools
Component: LTTng (show other bugs)
Version: unspecified   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: 2019-09-19 14:59 EDT by Genevieve Bastien CLA
Modified: 2019-09-30 09:30 EDT (History)
0 users

See Also:

Attachments
Trace to reproduce the problem (132.87 KB, application/x-compressed-tar)
2019-09-19 15:09 EDT, Genevieve Bastien CLA 		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 Genevieve Bastien CLA 2019-09-19 14:59:16 EDT 
On a recent laptop with nvme disk (not sure if that part is important, but that's the setup I have), wakeups from block device requests are handled in the context of the IRQ directly (no softirq). The IRQ number is somewhat arbitrary, so we cannot hard-code its link to the block device, but if dealing with LTTng statedump, we have block device names and interrupt names. If names prefixes match, we can link the source.

In any case, if we don't have the statedump information, the critical path should show an UNKNOWN blocking instead of PREEMPTED right now.
Comment 1 Genevieve Bastien CLA 2019-09-19 15:09:43 EDT 
Created attachment 279939 [details]
Trace to reproduce the problem
Comment 2 Eclipse Genie CLA 2019-09-20 17:15:47 EDT 
New Gerrit change created: https://git.eclipse.org/r/149934