On Mon, Aug 29, 2016 at 6:45 PM, Thomas Gleixner wrote:
> Tracing will tell you exactly what's going on in the system.
Will, it seems that I lost my direction. But anyway, there are some
gains to revisit the old tests.
>>> I've checked the /proc/timer_stats, /proc/interrupts, and perf, all
>>> th
On Sat, 27 Aug 2016, Mac Lin wrote:
> Hi Vegard,
> Thanks for the prompt response.
> The commit is introduced since 4.6, but the issue can be reproduced at
> 3.10 (earliest I have ever test). And testing on buildroot+4.7 with
> the commit reverted, the issue still happen.
>
> In fact, I did a test
Hi Vegard,
Thanks for the prompt response.
The commit is introduced since 4.6, but the issue can be reproduced at
3.10 (earliest I have ever test). And testing on buildroot+4.7 with
the commit reverted, the issue still happen.
In fact, I did a test that ran a script that keep increase a counter
fo
On 26 August 2016 at 19:10, Mac Lin wrote:
> We were having issue with our userspace application which
> __sometimes__ result in high CPU sys usage at each execution. The high
> sys CPU usage persist until the application is killed.
[...]
> Googling found one issue that seems related, but no furth
Hi all,
We were having issue with our userspace application which
__sometimes__ result in high CPU sys usage at each execution. The high
sys CPU usage persist until the application is killed.
We simplified the application to just creating a timer and its handler
then does nothing, but looping and
5 matches
Mail list logo
