From: Arjan van de Ven <arjanv@redhat.com>
To: lgb@lgb.hu
Cc: AlberT@SuperAlberT.it, linux-kernel@vger.kernel.org
Subject: Re: hyperthreading
Date: Tue, 25 Nov 2003 11:16:36 +0100 [thread overview]
Message-ID: <1069755396.5214.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20031125100526.GE339@vega.digitel2002.hu>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Tue, 2003-11-25 at 11:05, Gábor Lénárt wrote:
> On Tue, Nov 25, 2003 at 10:48:51AM +0100, Emiliano 'AlberT' Gabrielli wrote:
\
> OK, but if this CPU does not support HT, then why 'ht' is shown at
> flags in /proc/cpuinfo? It looks like quite illogical for me then ...
/proc/cpuinfo only reports what the cpu reports. The 'ht' flag means not
HyperThreading per se. It means it listens to the "rep; nop" sequence
for example. Also all Hyperthreading capable cpus have this flag set,
but that is a one way relationship. Esp since this needs more support
than just the cpu.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-25 11:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 9:44 hyperthreading Gábor Lénárt
2003-11-25 9:48 ` hyperthreading Emiliano 'AlberT' Gabrielli
2003-11-25 10:05 ` hyperthreading Gábor Lénárt
2003-11-25 10:16 ` Arjan van de Ven [this message]
2003-11-25 10:32 ` hyperthreading Måns Rullgård
2003-11-25 10:45 ` hyperthreading Mikael Pettersson
2003-11-29 13:29 ` hyperthreading Bill Davidsen
2003-12-01 10:53 ` hyperthreading Emiliano 'AlberT' Gabrielli
2003-11-25 10:22 ` hyperthreading Karl Pitrich
-- strict thread matches above, loose matches on Subject: below --
2002-08-22 12:58 Hyperthreading Nir Soffer
2002-08-22 14:30 ` Hyperthreading Hugh Dickins
2002-08-22 9:15 Hyperthreading Marc Dietrich
2002-08-22 14:06 ` Hyperthreading Hugh Dickins
2002-08-22 14:36 ` Hyperthreading Marc Dietrich
2002-08-21 22:56 Hyperthreading Nakajima, Jun
2002-08-21 23:45 ` Hyperthreading Alan Cox
2002-08-21 11:32 Hyperthreading Reed, Timothy A
2002-08-21 13:48 ` Hyperthreading James Bourne
2002-08-21 17:33 ` Hyperthreading Hugh Dickins
2002-08-21 19:34 ` Hyperthreading James Bourne
2002-08-21 21:16 ` Hyperthreading Kelsey Hudson
2002-08-21 21:55 ` Hyperthreading Banai Zoltan
2002-08-22 8:05 ` Hyperthreading venom
2002-08-26 19:00 ` Hyperthreading Kelsey Hudson
2002-08-22 8:00 ` Hyperthreading venom
2002-08-23 7:28 ` Hyperthreading Gilad Ben-Yossef
2002-08-23 8:10 ` Hyperthreading Hugh Dickins
2002-08-23 8:27 ` Hyperthreading Alan Cox
2002-08-23 8:12 ` Hyperthreading venom
2002-04-18 1:52 Hyperthreading Holzrichter, Bruce
2002-04-17 20:34 Hyperthreading Holzrichter, Bruce
2002-04-17 22:48 ` Hyperthreading Martin J. Bligh
2002-04-18 1:21 ` Hyperthreading James Bourne
2002-04-17 20:02 SMP P4 APIC/interrupt balancing James Bourne
2002-04-17 21:10 ` Hyperthreading Martin J. Bligh
2002-04-17 20:15 ` Hyperthreading Robert Love
2002-04-17 20:23 ` Hyperthreading Dave Jones
2002-04-17 21:24 ` Hyperthreading Jeff V. Merkey
2002-04-17 20:25 ` Hyperthreading James Bourne
2002-04-17 21:26 ` Hyperthreading Jeff V. Merkey
2002-04-18 0:31 ` Hyperthreading Martin J. Bligh
2002-04-18 4:50 ` Hyperthreading Jeff V. Merkey
2002-04-17 22:12 ` Hyperthreading Alan Cox
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=1069755396.5214.2.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=AlberT@SuperAlberT.it \
--cc=lgb@lgb.hu \
--cc=linux-kernel@vger.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