linux-kernel - Re: [PATCH 0/3] Improve TSC as a clocksource under VMware

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: <48FD6EDC.5010801@redhat.com>
Date:	Tue, 21 Oct 2008 01:55:40 -0400
From:	Chris Snook <csnook@...hat.com>
To:	akataria@...are.com
CC:	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Dan Hecht <dhecht@...are.com>, Jeff Hansen <x@...fhansen.com>
Subject: Re: [PATCH 0/3] Improve TSC as a clocksource under VMware

Alok Kataria wrote:
> This patch set makes some changes to the TSC code, so that it is always
> used as the default clocksource when running under VMware.
> The first 2 patches do the ground work of adding code to detect if we
> are running under VMware.
> The third patch adds a tsc_reliable flag which tells us that TSC is
> reliable on this system, so that we can skip some tests which can
> potentially mark TSC as unstable. Details under individual patch
> headers. 

Do you intend for this to supplement Jeff Hansen's tsc=stable patch, or to 
replace it?  If you intend to supplement it, you should rework your submission 
to make sure that both your autodetection and his command-line option use the 
same internal mechanism, and if you intend to replace it, you should say this 
explicitly, and justify it.  Either way, you should definitely CC Jeff on the 
submission, as I am doing now.

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