linux-kernel - Re: REGRESSION: the new i386 timer code fails to sync CPUs

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: <20060730215509.GA3662@kiste.smurf.noris.de>
Date:	Sun, 30 Jul 2006 23:55:09 +0200
From:	Matthias Urlichs <smurf@...rf.noris.de>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andi Kleen <ak@....de>, Andrew Morton <akpm@...l.org>,
	john stultz <johnstul@...ibm.com>,
	linux-kernel@...r.kernel.org, torvalds@...l.org, bunk@...sta.de,
	lethal@...ux-sh.org, hirofumi@...l.parknet.co.jp,
	asit.k.mallick@...el.com
Subject: Re: REGRESSION: the new i386 timer code fails to sync CPUs

Hi,

Arjan van de Ven:
> if the hardware side is different *speed*.. then a tsc sync ain't going
> to work... sure we write to it but it's immediately out of sync again
> 
No, it's in fact the same speed -- the BIOS just reads it wrongly.

I checked: the two date values do advance at the same rate.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@...rf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
"We need not invite the Devil to our table; he is too ready to come
 without being asked. The air all about us is filled with demons...."
                    [Martin Luther]
-
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/