public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ethan Weinstein <lists@stinkfoot.org>
To: linux-kernel@vger.kernel.org
Cc: William Lee Irwin III <wli@holomorphy.com>
Subject: Re: HT apparently not detected properly on 2.4.23
Date: Wed, 03 Dec 2003 18:41:36 -0500	[thread overview]
Message-ID: <3FCE74B0.9010506@stinkfoot.org> (raw)
In-Reply-To: <20031203224023.GV8039@holomorphy.com>

William Lee Irwin III wrote:

> On Wed, Dec 03, 2003 at 01:46:38PM -0500, Ethan Weinstein wrote:
> 
>>With 2.4.22, my Supermicro X5DPL-iGM-O (E7501 chipset) with 2 
>>xeons@2.4ghz and hypertherading enabled shows 4 cpu's in 
>>/proc/cpuinfo|proc/interrupts, with:
>>CONFIG_ACPI=y
>>CONFIG_ACPI_HT_ONLY=y
>>The same config with 2.4.23 only shows 2 cpus, even with:
>>CONFIG_NR_CPUS=4
>>Also, I believe this has been reported before, but the system only seems 
>>to interrupt on CPU0 with either kernel, unless I apply a patch I found 
>>here:
>>http://www.hardrock.org/kernel/2.4.22/irqbalance-2.4.22-MRC.patch
>>or run the `irqbalance' program.. which I don't care to do.  This 
>>problem _seems_ to be isolated to the Supermicro, as HT does seem 
>>properly detected on several other SMP systems I have at work (compaq 
>>ML370/ML380) with 2.4.23
> 
> You probably have sparse physical APIC ID's.
> 
Ok, setting CONFIG_NR_CPUS=8 does indeed solve the HT issue, looks like 
it was the numbering scheme:

Dec  3 18:32:28 spicymeatball kernel: CPU 0 (0x0000) enabled
Dec  3 18:32:28 spicymeatball kernel: Processor #0 Pentium 4(tm) 
XEON(tm) APIC version 16
Dec  3 18:32:28 spicymeatball kernel: LAPIC (acpi_id[0x0001] id[0x6] 
enabled[1])
Dec  3 18:32:28 spicymeatball kernel: CPU 1 (0x0600) enabled
Dec  3 18:32:28 spicymeatball kernel: Processor #6 Pentium 4(tm) 
XEON(tm) APIC version 16
Dec  3 18:32:28 spicymeatball kernel: LAPIC (acpi_id[0x0002] id[0x1] 
enabled[1])
Dec  3 18:32:28 spicymeatball kernel: CPU 2 (0x0100) enabled
Dec  3 18:32:28 spicymeatball kernel: Processor #1 Pentium 4(tm) 
XEON(tm) APIC version 16
Dec  3 18:32:28 spicymeatball kernel: LAPIC (acpi_id[0x0003] id[0x7] 
enabled[1])
Dec  3 18:32:28 spicymeatball kernel: CPU 3 (0x0700) enabled
Dec  3 18:32:28 spicymeatball kernel: Processor #7 Pentium 4(tm) 
XEON(tm) APIC version 16

But we're still only interrupting on CPU0 with this kernel.


-Ethan



  reply	other threads:[~2003-12-03 23:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 18:46 HT apparently not detected properly on 2.4.23 Ethan Weinstein
2003-12-03 19:40 ` Andre Tomt
2003-12-03 19:56   ` Mike Fedyk
2003-12-03 20:30     ` Ethan Weinstein
2003-12-03 22:40 ` William Lee Irwin III
2003-12-03 23:41   ` Ethan Weinstein [this message]
2003-12-03 23:58     ` William Lee Irwin III
2003-12-04  0:18       ` Ethan Weinstein
2003-12-05 17:12       ` Marcelo Tosatti
2003-12-05 17:48         ` William Lee Irwin III
2003-12-05 18:07           ` Re[2]: " Russell "Elik" Rademacher
     [not found]             ` <3FD0CD65.5080307@stinkfoot.org>
2003-12-05 23:02               ` Russell "Elik" Rademacher
2003-12-05 23:28                 ` Ethan Weinstein
2003-12-05 23:31                   ` Re[2]: " Russell "Elik" Rademacher
2003-12-05 23:38                     ` William Lee Irwin III
2003-12-04  0:46     ` William Lee Irwin III

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=3FCE74B0.9010506@stinkfoot.org \
    --to=lists@stinkfoot.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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