public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>,
	David Daney <ddaney.cavm@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>, Chen Jie <chenj@lemote.com>,
	zhangfx <zhangfx@lemote.com>
Subject: Re: [PATCH] clocksource: Avoid selecting mult values that might overflow when adjusted
Date: Thu, 10 Nov 2011 16:05:21 +0100	[thread overview]
Message-ID: <20111110150521.GD29614@elte.hu> (raw)
In-Reply-To: <20111109014632.GA8124@zhy>


* Yong Zhang <yong.zhang0@gmail.com> wrote:

> On Tue, Nov 08, 2011 at 01:39:02PM -0800, John Stultz wrote:
> > On Tue, 2011-11-08 at 13:02 +0800, Yong Zhang wrote:
> > > On Mon, Nov 07, 2011 at 07:09:00PM -0800, John Stultz wrote:
> > > > Yong: Can you also give this a test run to make sure you don't see any
> > > > problems?
> > > 
> > > Still get warning (3.2-rc1 + your patch):
> > > 
> > > [    0.017009] ------------[ cut here ]------------
> > > [    0.022156] WARNING: at /build/linux/kernel/time/timekeeping.c:828 do_timer+0x402/0x4e0()
> > > [    0.035917] Adjusting jiffies more then 11% (1024068096 vs 1024064000)
> > 
> > Ah. We're tripping the warning here in early boot. We use jiffies as the
> > default clocksource initially even before it is registered and the
> > maxadj is then set. So since its null here, any adjustment triggers the
> > warning.
> > 
> > That's easy enough to avoid. Can you give this updated version a try to
> > make sure I didn't miss anything else?
> 
> This version boot well on my side.
> 
> echo acpi_pm > /sys/devices/system/clocksource/clocksource0/current_clocksource
> echo hpet > /sys/devices/system/clocksource/clocksource0/current_clocksource
> 
> both work well.
> 
> Tested-by: Yong Zhang <yong.zhang0@gmail.com>

John, mind sending a pull request for this, based against current 
tip:timers/core? I'm quite sure it will fix the boot warning i saw as 
well.

Thanks,

	Ingo

  reply	other threads:[~2011-11-10 15:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 20:01 [PATCH] clocksource: Avoid selecting mult values that might overflow when adjusted John Stultz
2011-11-03  3:10 ` Yong Zhang
2011-11-03  9:36   ` Américo Wang
2011-11-04  2:16     ` Yong Zhang
2011-11-03 12:05 ` Thomas Gleixner
2011-11-03 13:10   ` John Stultz
2011-11-03 13:26     ` Thomas Gleixner
2011-11-03 14:01       ` John Stultz
2011-11-03 14:09         ` John Stultz
2011-11-03 14:49           ` Thomas Gleixner
2011-11-03 14:52             ` Thomas Gleixner
2011-11-03 15:14               ` John Stultz
2011-11-03 21:10 ` Ingo Molnar
2011-11-04 13:11   ` John Stultz
2011-11-04 15:20     ` Ingo Molnar
2011-11-08  3:09   ` John Stultz
2011-11-08  3:11     ` Yong Zhang
2011-11-08  5:02     ` Yong Zhang
2011-11-08 21:39       ` John Stultz
2011-11-09  1:46         ` Yong Zhang
2011-11-10 15:05           ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-09  2:08 John Stultz

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=20111110150521.GD29614@elte.hu \
    --to=mingo@elte.hu \
    --cc=chenj@lemote.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yong.zhang0@gmail.com \
    --cc=zhangfx@lemote.com \
    /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