All of lore.kernel.org
 help / color / mirror / Atom feed
From: David van Hoose <david.vanhoose@comcast.net>
To: Robert Love <rml@ximian.com>
Cc: Phy Prabab <phyprabab@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Programtically tell diff between HT and real
Date: Wed, 16 Jun 2004 15:57:51 -0400	[thread overview]
Message-ID: <40D0A63F.9000809@comcast.net> (raw)
In-Reply-To: <1087411607.7869.3.camel@localhost>



Robert Love wrote:
> On Wed, 2004-06-16 at 13:56 -0400, Robert Love wrote:
> 
> 
>>Yah.  Look at /proc/cpuinfo.
>>
>>Virtual processors have different 'processor' values but the same
>>'physical id', while physical processors obviously have different values
>>for both.
> 
> 
> Oh, and if you just want to see if a processor supports HT - the 'ht'
> flag is set in 'flags' in /proc/cpuinfo.

Not always true. I have a non-HT Pentium4, but I still have ht in my 
flags. The same goes for a couple of dual Xeon's I work on at school. 
Aparently Intel disabled the HT on a lot of Pentium 4 and Xeon chips, 
but left the HT flag behind. My system even has the additional IO-APICs 
too. Hence why everytime I boot a UP kernel, I get an 'unexpected 
IO-APIC' message.

Cheers,
David

  reply	other threads:[~2004-06-16 19:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 17:46 Programtically tell diff between HT and real Phy Prabab
2004-06-16 17:56 ` Robert Love
2004-06-16 18:46   ` Robert Love
2004-06-16 19:57     ` David van Hoose [this message]
2004-06-16 20:01       ` Phy Prabab
2004-06-16 20:03         ` Robert Love
2004-06-16 20:47     ` Richard B. Johnson
2004-06-16 21:36       ` Andre Tomt
2004-06-16 21:58         ` Richard B. Johnson
2004-06-16 17:59 ` lkml
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17  8:55 Mikael Pettersson
2004-06-17  8:55 Mikael Pettersson
2004-06-17 11:22 ` Richard B. Johnson
2004-06-17 11:52   ` Richard B. Johnson
     [not found] <fa.dpf28q3.1t6gfg5@ifi.uio.no>
     [not found] ` <fa.frt3cgc.l145hu@ifi.uio.no>
2004-06-18  3:20   ` Robert Hancock

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=40D0A63F.9000809@comcast.net \
    --to=david.vanhoose@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phyprabab@yahoo.com \
    --cc=rml@ximian.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.