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]

Message-ID: <4AFD07F0.70602@zytor.com>
Date:	Thu, 12 Nov 2009 23:17:04 -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/12/2009 09:59 AM, Ingo Molnar wrote:
>>
>> No, please.  We have had people who have "helpfully" tried to change 
>> /proc/cpuinfo in the past, and what we find is that application 
>> developers don't tell us -- they grumble among themselves and put out 
>> a new release saying "fixes breakage introduced by Linux ..."
>>
>> It's an ABI.  Keep it stable, please.
> 
> That's generally true, but i'm not suggesting that: i'm suggesting to 
> _clear_ the HT flag from the cpufeatures if there's only one sibling. 
> It's meaningless in that case and as the link quoted by the original 
> patch shows many people are confused by that.
> 
> I have such a box so i can test it. (but i dont expect any problems)
> 

Ah, okay, that makes more sense.  Someone else in the tread wanted to
rename the flag.

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