From: jeffy <jeffy.chen@rock-chips.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Nicholas Piggin <npiggin@gmail.com>,
akpm@linux-foundation.org, John Stultz <john.stultz@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Jonathan.Cameron@huawei.com, paulmck@linux.vnet.ibm.com,
mpe@ellerman.id.au, dzickus@redhat.com, sfr@canb.auug.org.au,
linuxarm@huawei.com, abdhalee@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [v2] timers: Fix excessive granularity of new timers after a nohz idle
Date: Wed, 23 Aug 2017 15:29:07 +0800 [thread overview]
Message-ID: <599D2EC3.2010900@rock-chips.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1708230900280.1821@nanos>
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 granularity of new timers after a nohz
>> idle)
>>
>> After revert it(or just add "!base->is_idle" check back), things work well...
>
> Can you please test V2?
>
hmm, v2 works...
Tested-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> Thanks,
>
> tglx
>
>
>
next prev parent reply other threads:[~2017-08-23 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 8:43 [PATCH v2] timers: Fix excessive granularity of new timers after a nohz idle Nicholas Piggin
2017-08-23 3:21 ` [v2] " jeffy
2017-08-23 3:35 ` Stephen Rothwell
2017-08-23 7:01 ` Thomas Gleixner
2017-08-23 7:29 ` jeffy [this message]
2017-08-24 9:42 ` [tip:timers/urgent] " tip-bot for Nicholas Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=599D2EC3.2010900@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sboyd@codeaurora.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox