Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] tracecompass Resources view doesn't make sense


The per-IRQ state seems a bit odd. Unless you have very long
threaded interrupt handlers running, I would not expect to
see that much overlap between interrupt handlers on a single

Can you provide the trace you are using, and info about this
current time/time range you are looking at ? Correlating
the text output (event-by-event) with the visual rendering should help
us learn more about what is going on here.



----- On Feb 3, 2017, at 6:38 AM, Mathieu Desnoyers mathieu.desnoyers@xxxxxxxxxxxx wrote:

> Alexandre,
> How well is the resource view of Trace Compass supposed to
> deal with events coming from perf ? I know it's been designed
> to handle lttng-modules events initially.
> Thanks,
> Mathieu
> ----- On Feb 3, 2017, at 4:59 AM, Joel Fernandes joelaf@xxxxxxxxxx wrote:
>> Hi,
>> I ran perf to collect some trace events an android device and
>> converted to CTF just to see what it looks like in tracecompass.
>> I find that in the 'Resources' view, when I click on the "+" next to
>> CPUx, the IRQs in the drop down appear to be active for much longer
>> than how they appear to be on the CPUx row itself. For example, in the
>> below screen shot [1], you can see this for CPU 0.
>> Am I doing something wrong?
>> I happen to enable a lot of events many which are not viewable in
>> tracecompass, I'm hoping those are ignored and doesn't cause problems.
>> Thanks,
>> [1]
> --
> Mathieu Desnoyers
> EfficiOS Inc.

Mathieu Desnoyers
EfficiOS Inc.

Back to the top