On 06/24/2014 02:41 PM, Viresh Kumar wrote:
On 24 June 2014 17:21, Daniel Lezcano daniel.lezcano@linaro.org wrote:
No traces for the cpu during a long period of time (except for entering idle) ?
Two things:
- I want to process data at runtime and start new sample as soon as
isolation gets interrupted.
Traces are good for analysis though and I am using them to check what's interrupting isolated core.
- Second there are cases, like what I reported to you for
ONESHOT_STOPPED bug. These spurious interrupts don't get traced at all..
Mmh, I saw your patch but I thought it was to spot the issue. Even if you enable all the traces, these wakeups are not shown ?