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]

Message-ID: <20090125145902.GV29067@pengutronix.de>
Date:	Sun, 25 Jan 2009 15:59:02 +0100
From:	Robert Schwebel <r.schwebel@...gutronix.de>
To:	john stultz <johnstul@...ibm.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Miklos Vajna <vmiklos@...galware.org>,
	Florian Fainelli <florian.fainelli@...ecomint.eu>,
	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

On Fri, Jan 23, 2009 at 05:36:30PM -0800, john stultz 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.
> 
> Florian: Is there any way we can check very early (ie: in setup_arch)
> for an RDC box?
> 
> Robert Schwebel, Sven Geggus: Either of you still maintaining the ELAN
> code?  Will the following from elanfreq_cpu_init catch all ELAN chips?
> 
>         if ((c->x86_vendor != X86_VENDOR_AMD) ||
>             (c->x86 != 4) || (c->x86_model != 10))

Nope, I don't have systems available any more with the ELAN.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
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/