mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: jeffy <jeffy.chen@rock-chips.com>
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 09:01:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1708230900280.1821@nanos> (raw)
In-Reply-To: <599CF4C4.2070703@rock-chips.com>

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?

Thanks,

	tglx

  parent reply	other threads:[~2017-08-23  7:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  8:43 [PATCH v2] " Nicholas Piggin
2017-08-23  3:21 ` [v2] " jeffy
2017-08-23  3:35   ` Stephen Rothwell
2017-08-23  7:01   ` Thomas Gleixner [this message]
2017-08-23  7:29     ` jeffy
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=alpine.DEB.2.20.1708230900280.1821@nanos \
    --to=tglx@linutronix.de \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=abdhalee@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dzickus@redhat.com \
    --cc=jeffy.chen@rock-chips.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=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

all inboxes | Powered by JetHome®