linux-kernel - Re: [GIT PULL] Additional x86 fixes for 2.6.31-rc5

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:	Mon, 10 Aug 2009 11:05:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Tan, Wei Chong" <wei.chong.tan@...el.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	John Stultz <johnstul@...ibm.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: Re: [GIT PULL] Additional x86 fixes for 2.6.31-rc5


* Tan, Wei Chong <wei.chong.tan@...el.com> wrote:

> > Thanks. I've zapped the original patch from x86/urgent. Linus's 
> > patch certainly looks feasible for .31 if it solves the problem 
> > and if we can merge it in the next few days.
> 
> Hi,
> 
> Linus's patch looks good to go.  I've tested it with 2 separate 
> versions of BIOS, each 1000 cycles, without any wrong CPU 
> frequency being reported.  In contrast, the same CPU/platform 
> without the patch will almost consistently report a wrong CPU 
> frequency once every 20 cycles and once every 50 cycles 
> respectively, for the 2 above mentioned BIOS.

Ok, i've created a changelog out of your and Linus's mail and have 
committed the fix to x86/urgent - the -tip commit notification bot 
will send it in a few minutes.

Linus, can i have your SOB line please?

	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/