From: Dave Jones <davej@redhat.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Fedora Kernel Team <kernel-team@fedoraproject.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: WARNING: Adjusting tsc more then 11%
Date: Mon, 5 Mar 2012 14:57:58 -0500 [thread overview]
Message-ID: <20120305195758.GA25498@redhat.com> (raw)
In-Reply-To: <1330977010.2191.84.camel@work-vm>
On Mon, Mar 05, 2012 at 11:50:10AM -0800, John Stultz wrote:
> > > > The reports seem to have started around 3.3-rc4.
> > thinking about this some more, while the reports starts around rc4, this
> > may have been caused by something prior to that, as anyone moving from
> > Fedora 16 or earlier to F17 alpha would have jumped quite a kernel version or two.
>
> Was F16 3.1 based? The warning was added in 3.2, so if you skipped it,
> it may not be new behavior then.
initially 3.1 based. We recently pushed out a rebase to 3.2.
This bug hasn't shown up there (yet?)
> Ok. Well, just to level set: the warning is informative, and points to
> unexpected, but not necessarily unsafe behavior.
>
> In fact, the risk (where mult is adjusted to be large enough to cause an
> overflow) we're warning about have been present 2.6.36 or even possibly
> before. The change in 3.2 which added the warning also added a more
> conservative mult calculation, so we're less likely to get overflow
> prone large mult values.
>
> So it would be great to get further feedback from folks who are seeing
> this warning, so we can really hammer this out, but I don't want the
> warning spooking anyone into thinking things are terribly broken.
One of the reports was from someone using vbox. I'm now wondering if
the other users are using some other flavour of virt. I'll ask.
Dave
next prev parent reply other threads:[~2012-03-05 19:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 15:44 WARNING: Adjusting tsc more then 11% Dave Jones
2012-03-05 18:32 ` John Stultz
2012-03-05 19:23 ` Dave Jones
2012-03-05 19:50 ` John Stultz
2012-03-05 19:56 ` Josh Boyer
2012-03-05 20:24 ` John Stultz
2012-03-05 20:28 ` Josh Boyer
2012-03-05 20:41 ` John Stultz
2012-03-05 19:57 ` Dave Jones [this message]
2012-03-05 20:16 ` Sasha Levin
2012-03-05 20:27 ` John Stultz
2012-03-05 20:36 ` Sasha Levin
2012-03-07 1:13 ` John Stultz
2012-03-22 19:11 ` Sasha Levin
2012-03-22 19:21 ` John Stultz
2012-03-22 15:28 ` Dave Jones
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=20120305195758.GA25498@redhat.com \
--to=davej@redhat.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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