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: <20091112065930.GA9279@elte.hu>
Date:	Thu, 12 Nov 2009 07:59:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	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


* 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.

Hm?

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