mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: HT not active
Date: Mon, 14 Aug 2006 22:10:25 +1000	[thread overview]
Message-ID: <9327.1155557425@ocs10w.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 14 Aug 2006 13:38:22 +0200." <Pine.LNX.4.61.0608141335550.7970@yvahk01.tjqt.qr>

Jan Engelhardt (on Mon, 14 Aug 2006 13:38:22 +0200 (MEST)) wrote:
>Hello list,
>
>
>
>I cannot get HT to be used on some machine:
>
>w04a# cat /proc/cpuinfo 
>processor       : 0
>vendor_id       : GenuineIntel
>cpu family      : 15
>model           : 0
>model name      : Intel(R) Pentium(R) 4 CPU 1700MHz
>stepping        : 10
>cpu MHz         : 1694.890
>cache size      : 256 KB
>fdiv_bug        : no
>hlt_bug         : no
>f00f_bug        : no
>coma_bug        : no
>fpu             : yes
>fpu_exception   : yes
>cpuid level     : 2
>wp              : yes
>flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
>cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up
>bogomips        : 3393.46
>
>'ht' indicates:
>#define X86_FEATURE_HT          (0*32+28) /* Hyper-Threading */                 
>
>so I installed an SMP kernel, which has
>CONFIG_SMP=y
>CONFIG_SUSPEND_SMP=y
>CONFIG_X86_FIND_SMP_CONFIG=y
>CONFIG_SCHED_SMT=y
>CONFIG_X86_HT=y
>
>yet it shows the 'up' flag in cpuinfo
>#define X86_FEATURE_UP          (3*32+ 9) /* smp kernel running on up */
>
>What could be missing? Some BIOS option perhaps?
>Thanks for any hints.

It could be BIOS HT settings.  You could also need CONFIG_ACPI, I have
seen HT systems which required ACPI before Linux could see the extra
threads.


  parent reply	other threads:[~2006-08-14 12:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 11:38 Jan Engelhardt
2006-08-14 11:46 ` Michal Piotrowski
2006-08-14 11:55   ` Jan Engelhardt
2006-08-14 12:10 ` Keith Owens [this message]
2006-08-14 16:19   ` Len Brown
2006-08-14 12:36 ` Alan Cox
2006-08-15 14:39   ` Mark Lord
2006-08-14 15:19 ` Arjan van de Ven
2006-08-14 15:23   ` Jan Engelhardt
2006-08-14 12:06 Mikael Pettersson
2006-08-14 12:47 ` Jan Engelhardt
     [not found] <fa.YLv8m2Uw0It/GRKxQHnEfBS+Dao@ifi.uio.no>
2006-08-14 14:23 ` Robert Hancock
2006-08-14 14:51   ` linux-os (Dick Johnson)
2006-08-14 15:32     ` Lennart Sorensen
2006-08-14 16:02       ` linux-os (Dick Johnson)
2006-08-14 17:11         ` Lennart Sorensen
2006-08-14 17:51           ` Jan Engelhardt
2006-08-15 17:47             ` H. Peter Anvin

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=9327.1155557425@ocs10w.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=jengelh@linux01.gwdg.de \
    --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

all inboxes | Powered by JetHome®