[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130715173848.GA1066@redhat.com>
Date: Mon, 15 Jul 2013 13:38:48 -0400
From: Dave Jones <davej@...hat.com>
To: Frederic Weisbecker <fweisbec@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
rostedt@...dmis.org
Subject: Re: nohz: Warn if the machine can not perform nohz_full
On Mon, Jul 15, 2013 at 01:24:23PM -0400, Dave Jones wrote:
> On Mon, Jul 15, 2013 at 07:18:02PM +0200, Frederic Weisbecker wrote:
>
> > > So I guess you guys never want this to be enabled on distro kernels ?
> > > If that's the case, can you add something to that effect in Kconfig ?
> >
> > I believe we want it to be enabled on distros in the long term. But right now it would
> > be a bad idea until the off case (nohz_full= parameter empty) is carefully optimized.
> > I'm currently working on that.
> >
> > Now for the unstable tsc, which is what it's about on the above code block, we need
> > the tick to be there to leverage the sched clock madness. May be there could be some
> > other solution that could work along full dynticks but for now we chose the easy path.
> >
> > Are broken TSCs that common?
>
> I just hit one apparently. http://paste.fedoraproject.org/25421/73907845/raw/
> That's a fairly recent Atom board, so I suspect it's not uncommon on that platform.
And here's a Core Duo from circa 2008.
http://paste.fedoraproject.org/25429/13739098/raw
Two for two so far. I get the feeling you guys are going to get a ton of these reports.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists