public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jack F. Vogel" <jfv@trane.bluesong.net>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	Andrew Theurer <habanero@us.ibm.com>,
	linux-kernel@vger.kernel.org
Cc: cleverdj@us.ibm.com
Subject: Re: Hyperthreading and physical/logical CPU identification
Date: Tue, 30 Apr 2002 10:00:01 -0700	[thread overview]
Message-ID: <200204301700.g3UH01v04279@Bluesong.NET> (raw)
In-Reply-To: <200204291849.NAA23906@popmail.austin.ibm.com> <26950000.1020120115@flay>

On Monday 29 April 2002 03:41 pm, Martin J. Bligh wrote:
> > The problem is, I have 4 physical processors, but kernel.org kernels so
> > far do not recognize all of them.  2.4.18 will find 3, while 2.5.11 will
> > find only 2 (BIOS hyperthreading support off, no acpismp=force). 
> > However, on 2.5.11, if I enable hyperthreading (thru BIOS and
> > acpismp=force, I see 4 processors.
>
> When you say the kernel doesn't recognise all of the physical processors,
> do you mean it doesn't see them in the MPS/ACPI table, or that they fail to
> boot? Can you post your boot log?
>
> I see you have a "us.ibm.com" email address ... is this machine an x440,
> one of it's smaller brethren, or something totally different?

If it is the x440 then the problem is the xapic and you need James Cleverdon's
summit patch for all processors to be seen and properly initialized. Email
James or me if you need a pointer.

-- 
Jack F. Vogel
IBM  Linux Solutions
jfv@us.ibm.com  (work)
jfv@Bluesong.NET (home)

  reply	other threads:[~2002-04-30 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29 18:31 Hyperthreading and physical/logical CPU identification Andrew Theurer
2002-04-29 22:41 ` Martin J. Bligh
2002-04-30 17:00   ` Jack F. Vogel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-29 19:40 Grover, Andrew
2002-04-29 19:59 ` Andrew Theurer
2002-04-29 22:20   ` J.A. Magallon
2002-04-29 23:14 ` Jauder Ho
2002-04-29 20:41 Holzrichter, Bruce

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=200204301700.g3UH01v04279@Bluesong.NET \
    --to=jfv@trane.bluesong.net \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=cleverdj@us.ibm.com \
    --cc=habanero@us.ibm.com \
    --cc=jfv@bluesong.net \
    --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