From: Greg Norris <haphazard@kc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test3] Hyperthreading gone
Date: Sun, 10 Aug 2003 07:00:32 -0500 [thread overview]
Message-ID: <20030810120032.GA14437@glitch.localdomain> (raw)
In-Reply-To: <87oeyyc7u9.fsf@deneb.enyo.de>
On Sun, Aug 10, 2003 at 09:03:42AM +0200, Florian Weimer wrote:
> I didn't. Previous experience (with some 2.5.x versions) indicates
> that Linux does not support full ACPI on this machine. The
> documentation suggests that the command line option enables full ACPI,
> so I hesitate to do this.
According to the 2.6.0-test3 menuconfig help text, the parameter is
required when CPU Enumeration Only is selected, and enables only
limited ACPI support. For whatever it's worth, that matches my
experience.
CONFIG_ACPI_HT_ONLY:
This option enables limited ACPI support -- just enough to
enumerate processors from the ACPI Multiple APIC Description
Table (MADT). Note that ACPI supports both logical (e.g. Hyper-
Threading) and physical processors, where the MultiProcessor
Specification (MPS) table only supports physical processors.
Full ACPI support (CONFIG_ACPI) is preferred. Use this option
only if you wish to limit ACPI's role to processor enumeration.
In this configuration, ACPI defaults to off. It must be enabled
on the command-line with the "acpismp=force" option.
next prev parent reply other threads:[~2003-08-10 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 17:08 Florian Weimer
2003-08-09 21:10 ` Gabor MICSKO
2003-08-09 22:17 ` Greg Norris
2003-08-10 7:03 ` Florian Weimer
2003-08-10 12:00 ` Greg Norris [this message]
2003-08-11 7:13 ` Florian Weimer
2003-08-11 16:52 ` Hugh Dickins
2003-08-11 18:12 ` Florian Weimer
2003-08-11 18:35 ` Hugh Dickins
2003-08-12 16:05 Brown, Len
2003-08-12 17:02 ` Marcelo Tosatti
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=20030810120032.GA14437@glitch.localdomain \
--to=haphazard@kc.rr.com \
--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®