linux-kernel - Re: [PATCH RFC] x86: fix confusing name of /proc/cpuinfo "ht" flag

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]

Date:	Wed, 11 Nov 2009 23:08:10 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Dave Jones <davej@...emonkey.org.uk>
Subject: Re: [PATCH RFC] x86: fix confusing name of /proc/cpuinfo "ht" flag

On 11/11/2009 10:59 PM, Ingo Molnar wrote:
> 
> * Bartlomiej Zolnierkiewicz <bzolnier@...il.com> wrote:
> 
>> "ht" flag indicates only ability to detect siblings not HT presence 
>> itself.
>>
>> Inspired by:
>> http://www.codemonkey.org.uk/2009/11/10/common-hyperthreading-misconception/
> 
> i think instead of changing 'ht' to 'ht_detect', it would be even more 
> intuitive to only expose the 'ht' flag if the ht-detect capability is 
> there _and_ if the number of siblings is 2 or more.
> 
> That way we dont change it - we just 'hide' the 'ht' string on the 
> category of systems that can enumerate HT via the CPUID but dont 
> actually have HyperThreading.
> 

/proc/cpuinfo is a user-space visible ABI.  Changing it is bad chicken.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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