From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: Hyper-threading
Date: Mon, 02 Jun 2003 12:29:55 -0400 [thread overview]
Message-ID: <3EDB7B83.1020108@coyotegulch.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0306021147460.31561-100000@router.windsormachine.com>
Mike Dresser wrote:
> Indeed, I saw that. On the P4 2.66ghz that you have, the "second" cpu is
> disabled by intel, as they sell hyperthreading only on the newer Xeon P4
> (which you don't have), and the new 800FSB (4x200) units, which again
> you don't have.
>
> ..... CPU clock speed is 2672.7802 MHz.
> ..... host bus clock speed is 133.6388 MHz.
Some Pentium 4 chips support HT even when they officially "don't". For
example, my system has an Intel MB and a Pentium 4 2.8GHz processor; it
boots using HT just fine. From a recent boot:
Tycho kernel: CPU1: Intel Pentium 4 (Northwood) stepping 07
Tycho kernel: Total of 2 processors activated (11042.81 BogoMIPS).
Tycho kernel: cpu_sibling_map[0] = 1
Tycho kernel: cpu_sibling_map[1] = 0
Tycho kernel: ENABLING IO-APIC IRQs
Tycho kernel: Setting 2 in the phys_id_present_map
Tycho kernel: ...changing IO-APIC physical APIC ID to 2 ... ok.
Tycho kernel: ..TIMER: vector=0x31 pin1=2 pin2=0
Tycho kernel: testing the IO APIC.......................
Tycho kernel: .................................... done.
Tycho kernel: Using local APIC timer interrupts.
Tycho kernel: calibrating APIC timer ...
Tycho kernel: ..... CPU clock speed is 2783.0819 MHz.
Tycho kernel: ..... host bus clock speed is 132.0562 MHz.
Tycho kernel: checking TSC synchronization across 2 CPUs: passed.
Tycho kernel: Starting migration thread for cpu 0
Tycho kernel: Bringing up 1
Tycho kernel: CPU 1 IS NOW UP!
Tycho kernel: Starting migration thread for cpu 1
Tycho kernel: CPUS done 2
Note the "132.0562" MHz bus speed.
I obtained my system directly from Intel; however, I know of a few
people who obtained Pentium 4 chips from retailers, and their processors
support HT with a 4x133 bus.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Professional programming for science and engineering;
Interesting and unusual bits of very free code.
next prev parent reply other threads:[~2003-06-02 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 16:46 Hyper-threading Richard B. Johnson
2003-06-01 16:49 ` Hyper-threading DevilKin-LKML
2003-06-01 18:21 ` Hyper-threading Richard B. Johnson
2003-06-02 14:54 ` Hyper-threading Mike Dresser
2003-06-02 15:31 ` Hyper-threading Richard B. Johnson
2003-06-02 15:52 ` Hyper-threading Mike Dresser
2003-06-02 16:29 ` Scott Robert Ladd [this message]
2003-06-02 16:58 ` Hyper-threading Richard B. Johnson
2003-06-03 2:36 ` Hyper-threading Robert White
2003-06-01 17:30 ` [OT] Hyper-threading Philip Dodd
2003-06-02 6:11 ` Hyper-threading Martin Schlemmer
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 17:21 Hyper-threading Xose Vazquez Perez
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=3EDB7B83.1020108@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=mdresser_l@windsormachine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox