public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: mikpe@csd.uu.se
Cc: Steven Cole <elenstev@mesatop.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Samuel Flory <sflory@rackable.com>,
	John Appleby <john@dnsworld.co.uk>,
	xyko_ig@ig.com.br,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Wrong number of cpus detected/reported
Date: Wed, 11 Jun 2003 12:17:32 -0400	[thread overview]
Message-ID: <3EE7561C.9010202@techsource.com> (raw)
In-Reply-To: 16102.22713.50999.54138@gargle.gargle.HOWL



mikpe@csd.uu.se wrote:
> Steven Cole writes:
>  > On Tue, 2003-06-10 at 15:35, Alan Cox wrote:
>  > > > wp		: yes
>  > > > flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
>  > > > bogomips	: 2798.38
>  > > > 
>  > > > See that ht flag near the end?
>  > > 
>  > > The ht flag means the ht facilities (mtrr etc) are present, doesnt mean
>  > > HT necessarily is
>  > 
>  > Is there a reliable method, apart from knowing 'a priori' the mapping
>  > from CPU models and stepping to hyperthreading capability?
> 
> Yes. Execute cpuid with eax=1 on each CPU. ebx describes among other things
> the number of threads and which thread you're on. If you ever find yourself
> on a non-zero thread, you have HT.


I presume, however, that to get into a non-zero thread, you have to turn 
HT on.  That is, when the machine first powers up, there is nothing for 
the second thread to execute, so it's turned off.  (I'm assuming 
something similar for SMP boxes.)  So, the real question should be, 
before you attempt to turn on HT, how do you find out whether or you CAN 
turn on HT.



  reply	other threads:[~2003-06-11 15:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <434747C01D5AC443809D5FC5405011310B7169@bobcat.unickz.com>
2003-06-10 20:21 ` Wrong number of cpus detected/reported John Appleby
2003-06-10 20:36   ` Samuel Flory
2003-06-10 21:04     ` Steven Cole
2003-06-10 21:35       ` Alan Cox
2003-06-10 21:52         ` Steven Cole
2003-06-10 22:06           ` Alan Cox
2003-06-10 22:16           ` mikpe
2003-06-11 16:17             ` Timothy Miller [this message]
2003-06-11 16:28               ` mikpe
2003-06-11 21:26               ` Con Kolivas
2003-06-11  0:04 Lauro, John
     [not found] <434747C01D5AC443809D5FC5405011310B7190@bobcat.unickz.com>
2003-06-10 21:11 ` John Appleby
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10 20:35 Lauro, John
2003-06-10 18:50 José Francisco Ribeiro Neto
2003-06-10 20:17 ` David Schwartz
2003-06-10 21:08   ` Timothy Miller

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=3EE7561C.9010202@techsource.com \
    --to=miller@techsource.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=elenstev@mesatop.com \
    --cc=john@dnsworld.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=sflory@rackable.com \
    --cc=xyko_ig@ig.com.br \
    /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