linux-kernel - Re: PATCH: (v2) Allow user to force 'tsc' to be treated as stable.

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] [day] [month] [year] [list]

Message-ID:  <498DB9C6.6080501@gmail.com>
Date:	Sat, 07 Feb 2009 10:41:42 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject:  Re: PATCH:  (v2) Allow user to force 'tsc' to be treated as stable.

Ben Greear wrote:
> Allow user to force TSC to be treated as a stable clock-source.
> On some systems, with ACPI disabled in the BIOS, the
> kernel determines that the TSC is unstable, when it fact
> it appears to be fine.  This patch allows one to force
> the kernel to treat the tsc as stable.
> 
> This is against 2.6.29-rc3.
> 
> Signed-Off-By:  Ben Greear<greearb@...delatech.com>

I don't think this is a good solution. If the TSC is in fact stable it 
would be better to fix the detection to detect it as such. If it's not 
then this will cause problems.

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