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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 25 Jan 2009 16:02:55 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Florian Fainelli <florian.fainelli@...ecomint.eu>
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


* Florian Fainelli <florian.fainelli@...ecomint.eu> wrote:

> Le Saturday 24 January 2009 02:36:30 john stultz, vous avez écrit :
> > 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.
> >
> > Florian: Is there any way we can check very early (ie: in setup_arch)
> > for an RDC box?
> 
> Sorry for answering so late.
> 
> We cannot rely on the cpuid since there is not one, nor the bios, since 
> most (if not all) boards use RedBoot as a bootloader. If we have PCI 
> initiliazed, we could check the presence of a R6040 Ethernet MAC.
> [...]

yep, an early PCI quirk for that would suffice.

	Ingo

--
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/