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: <200706052331.09214.ak@suse.de>
Date:	Tue, 5 Jun 2007 23:31:08 +0200
From:	Andi Kleen <ak@...e.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lguest-fix-divide-error-implement-sched_clock

On Tuesday 05 June 2007 23:15:28 H. Peter Anvin wrote:
> Andi Kleen wrote:
> > 
> > I don't think it's a good idea for the TSC. There are various
> > setups where it is unreliable and also often simulators don't 
> > implement it correctly. And it's always a valuable workaround
> > to be able to turn it off.
> > 
> 
> For all I can tell, if this is the case, then CONFIG_X86_TSC should be
> removed completely.

Yes it should.

> We still support the TSC when CONFIG_X86_TSC is not 
> compiled in; that attribute controls if it is unconditionally required.
> 
> (We seem to still not always use it, which may be a good indication that
> CONFIG_X86_TSC has outlived its usefulness.  Should it be removed?)

Yes.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ