From: "Chris Friesen" <cfriesen@nortel.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.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
Date: Wed, 11 Nov 2009 14:46:16 -0600 [thread overview]
Message-ID: <4AFB2298.5040903@nortel.com> (raw)
In-Reply-To: <200911112134.34261.bzolnier@gmail.com>
On 11/11/2009 02:34 PM, Bartlomiej Zolnierkiewicz 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/
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> ---
> It could be that there are some user-space programs depending on "ht"
> flag so the patch is marked as RFC..
If a cpu is capable of ht but doesn't have any siblings, do we actually
care?
If many people consider the "ht" flag to indicate that hyperthreading is
actually available, what about instead changing the meaning of the "ht"
flag to indicate that there actually are siblings?
Chris
next prev parent reply other threads:[~2009-11-11 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:34 [PATCH RFC] x86: fix confusing name of /proc/cpuinfo "ht" flag Bartlomiej Zolnierkiewicz
2009-11-11 20:46 ` Chris Friesen [this message]
2009-11-12 17:07 ` Alexander Clouter
2009-11-11 21:35 ` Jeff Garzik
2009-11-12 6:59 ` Ingo Molnar
2009-11-12 7:08 ` H. Peter Anvin
2009-11-12 8:13 ` Ingo Molnar
2009-11-12 15:18 ` H. Peter Anvin
2009-11-12 17:59 ` Ingo Molnar
2009-11-12 18:37 ` Dave Jones
2009-11-12 19:49 ` H. Peter Anvin
2009-11-13 7:42 ` Ingo Molnar
2009-11-13 10:24 ` Bartlomiej Zolnierkiewicz
2009-11-13 7:17 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AFB2298.5040903@nortel.com \
--to=cfriesen@nortel.com \
--cc=bzolnier@gmail.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox