linux-kernel - Re: [PATCH 2/3] x86: Implement prctl PR_GET_TSC and PR_SET

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: <20080426.174735.117959877.davem@davemloft.net>
Date:	Sat, 26 Apr 2008 17:47:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hpa@...or.com
Cc:	dean@...tic.org, ejbosman@...vu.nl, mtk.manpages@...il.com,
	akpm@...ux-foundation.org, tglx@...utronix.de, mingo@...hat.com,
	andrea@...share.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, arjan@...radead.org
Subject: Re: [PATCH 2/3] x86: Implement prctl PR_GET_TSC and PR_SET_TSC

From: "H. Peter Anvin" <hpa@...or.com>
Date: Sat, 26 Apr 2008 17:37:17 -0700

> dean gaudet wrote:
> >>>
> >> PR_SET/PR_GET are the common prefixes, though.
> > 
> > that's not what's at issue... "PR_SET_TSC" reads "set the TSC" ... it 
> > doesn't read "set the ability to use the rdtsc instruction". 
> > PR_SET_RDTSC_ENABLE would seem to be more accurate... or even 
> > PR_SET_CR4_TSD which is what it really does :)
> > 
> 
> The whole point I'm making is that any such name would inherently read 
> x86-specific.

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