Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756834AbZAXJPD (ORCPT ); Sat, 24 Jan 2009 04:15:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750976AbZAXJOq (ORCPT ); Sat, 24 Jan 2009 04:14:46 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:43880 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750806AbZAXJOo (ORCPT ); Sat, 24 Jan 2009 04:14:44 -0500 Date: Sat, 24 Jan 2009 10:14:04 +0100 From: Ingo Molnar To: john stultz Cc: Miklos Vajna , Florian Fainelli , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "Rafael J. Wysocki" , Gabriel C , =?iso-8859-1?Q?CS=C9CSY_L=E1szl=F3?= , r.schwebel@pengutronix.de, sven@geggus.net Subject: Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade Message-ID: <20090124091404.GA32032@elte.hu> References: <20090121171423.GI21473@genesis.frugalware.org> <1f1b08da0901211200l88fa89s78a51c4e90878d85@mail.gmail.com> <20090121210726.GK21473@genesis.frugalware.org> <1232573646.6997.21.camel@localhost.localdomain> <20090122195132.GZ21473@genesis.frugalware.org> <20090122235727.GB21473@genesis.frugalware.org> <1232674994.6678.45.camel@localhost.localdomain> <20090123110439.GK15188@elte.hu> <1f1b08da0901231736u46d8981ckc4b89ac66d7d8a5e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1f1b08da0901231736u46d8981ckc4b89ac66d7d8a5e@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1313 Lines: 29 * john stultz wrote: > On Fri, Jan 23, 2009 at 3:04 AM, Ingo Molnar wrote: > > * john stultz wrote: > >> I'd think this would ideally be more of a subarch in the config > >> selection like the AMD Elan is, so folks know it really is not just a > >> extra-support feature and in fact limits what hardware you can use the > >> resulting kernel on. > > > > a better solution is that if RDC is set [it is unset by default] we should > > turn PIT_TICK_RATE into a variable, defaulting it to 1193182. If a real > > RDC or ELAN system is running, that variable is changed during early > > bootup, in the init functions for those platforms. > > Took a quick look at this, and I don't see any detection code for either > RDC. The X86_ELAN config also has no conditionals, but maybe the elan > cpufreq code can help here. i'd suggest to just remove the #ifdef for now (it's causing problems) and add the variable - we can add the quirks for those two platforms later on, separately from your patch(es). Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/