Date: Thu, 12 Nov 2009 07:59:30 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
       "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
       Dave Jones <davej@codemonkey.org.uk>
Subject: Re: [PATCH RFC] x86: fix confusing name of /proc/cpuinfo "ht" flag
Message-ID: <20091112065930.GA9279@elte.hu>
References: <200911112134.34261.bzolnier@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200911112134.34261.bzolnier@gmail.com>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 854
Lines: 25


* Bartlomiej Zolnierkiewicz <bzolnier@gmail.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/