linux-kernel - Re: PATCH: 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090205195945.GE3129@elte.hu>
Date:	Thu, 5 Feb 2009 20:59:45 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Ben Greear <greearb@...delatech.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>, rusty@...tcorp.com.au
Subject: Re: PATCH:  Allow user to force 'tsc' to be treated as stable.


* Ben Greear <greearb@...delatech.com> wrote:

> Allow user to force TSC as stable clock-source.
> Works around BIOS issues in the FWA-7304 (Via CN700 chipset)
> system, and possibly others.
>
> This is against 2.6.29-rc3.

What 'issues' does that work around, exactly?

	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/