Hi Thomas,
On 08/23/2017 03:01 PM, Thomas Gleixner wrote:
On Wed, 23 Aug 2017, jeffy wrote:
Hi guys,
I was testing a arm64 based device(chromebook bob), and the kernel hang a
lot(during booting or suspending) on for-next(next-20170822) with this commit:
71acb768f5b3 (timers: Fix excessive gra
On Wed, 23 Aug 2017, jeffy wrote:
> Hi guys,
>
> I was testing a arm64 based device(chromebook bob), and the kernel hang a
> lot(during booting or suspending) on for-next(next-20170822) with this commit:
> 71acb768f5b3 (timers: Fix excessive granularity of new timers after a nohz
> idle)
>
> Aft
Hi jeffy,
On Wed, 23 Aug 2017 11:21:40 +0800 jeffy wrote:
>
> I was testing a arm64 based device(chromebook bob), and the kernel hang
> a lot(during booting or suspending) on for-next(next-20170822) with this
> commit:
> 71acb768f5b3 (timers: Fix excessive granularity of new timers after a
> n
Hi guys,
I was testing a arm64 based device(chromebook bob), and the kernel hang
a lot(during booting or suspending) on for-next(next-20170822) with this
commit:
71acb768f5b3 (timers: Fix excessive granularity of new timers after a
nohz idle)
After revert it(or just add "!base->is_idle" chec
When a timer base is idle, it is forwarded when a new timer is added
to ensure that granularity does not become excessive. When not idle,
the timer tick is expected to increment the base.
However there are several problems:
- If an existing timer is modified, the base is forwarded only after
th
5 matches
Mail list logo
