linux-kernel - Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200901251638.34040.florian.fainelli@telecomint.eu>
Date:	Sun, 25 Jan 2009 16:38:32 +0100
From:	Florian Fainelli <florian.fainelli@...ecomint.eu>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	john stultz <johnstul@...ibm.com>,
	Miklos Vajna <vmiklos@...galware.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Gabriel C <nix.or.die@...glemail.com>,
	CSÉCSY László <boobaa@...galware.org>,
	r.schwebel@...gutronix.de, sven@...gus.net
Subject: Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade

Le Sunday 25 January 2009 16:03:49 Ingo Molnar, vous avez écrit :
> * Florian Fainelli <florian.fainelli@...ecomint.eu> wrote:
> > Le Saturday 24 January 2009 10:14:04 Ingo Molnar, vous avez écrit :
> > > * john stultz <johnstul@...ibm.com> wrote:
> > > > On Fri, Jan 23, 2009 at 3:04 AM, Ingo Molnar <mingo@...e.hu> wrote:
> > > > > * john stultz <johnstul@...ibm.com> 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).
> >
> > Fine with me. Ingo, is there any infrastructure yet to get an early
> > quirk set the PIT tick rate accordingly ?
>
> Not yet but it should be easy - do you have the time to implement it?

Not until a week, sorry.

Thanks
-- 
Cordialement, Florian Fainelli
------------------------------
--
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/