linux-kernel - Re: [PATCH] All Transmeta CPUs have constant TSCs

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: <45A2D9C8.9020007@zytor.com>
Date:	Mon, 08 Jan 2007 15:54:48 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	dean gaudet <dean@...tic.org>
CC:	Jan Engelhardt <jengelh@...ux01.gwdg.de>, akpm@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] All Transmeta CPUs have constant TSCs

dean gaudet wrote:
> On Mon, 8 Jan 2007, H. Peter Anvin wrote:
> 
>> I *definitely* support the concept that RDPMC 0 should could CPU cycles by
>> convention in Linux.
> 
> unfortunately that'd be very limiting and annoying on core2 processors 
> which have dedicated perf counters for clocks unhalted (actual vs. 
> nominal), but only 2 configurable perf counters.  i forget what ecx value 
> gets you the dedicated counters... but a solution which might work would 
> be a syscall to return the perf counter number...
> 
> or we could just merge perfmon ;)
> 

OK, if there are dedicated counters in hardware at a different number, 
we probably should make it an ELF entry value (no need to make it a 
syscall for a constant.)

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