From: Frederic Weisbecker <fweisbec@gmail.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: Warning: NO_HZ FULL will not work with unstable sched clock
Date: Mon, 11 Nov 2013 18:20:29 +0100 [thread overview]
Message-ID: <20131111172028.GF26853@localhost.localdomain> (raw)
In-Reply-To: <CAA1sL1SNn7O5CQbJn+dC5EjJKM-kfZq+brWLotC7LCNYVNBmeQ@mail.gmail.com>
On Sat, Nov 09, 2013 at 12:32:06PM +0400, Alexander Beregalov wrote:
> Hi,
> It first appeared some time after 3.9 or 3.10 and still persist.
> I guess bisect is not required?
>
> WARNING: CPU: 1 PID: 6 at kernel/time/tick-sched.c:187
> can_stop_full_tick+0x8d/0x9a()
> NO_HZ FULL will not work with unstable sched clock
Right, it's not a bug, just a warning we've put to make sure that users of
full dynticks are aware of limitations when the sched clock is unstable.
That's something we want to fix in the long run as it seems that quite
a lot of people have unstable tsc.
Thanks.
prev parent reply other threads:[~2013-11-11 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 8:32 Warning: NO_HZ FULL will not work with unstable sched clock Alexander Beregalov
2013-11-11 17:20 ` Frederic Weisbecker [this message]
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=20131111172028.GF26853@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).