From: Juan Quintela <quintela@trasno.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: "'Arjan van de Ven'" <arjanv@redhat.com>,
Hugh Dickins <hugh@veritas.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
Andrew Morton <akpm@digeo.com>,
torvalds@transmeta.com, acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] acpismp=force fix
Date: Mon, 30 Jun 2003 17:42:29 +0200 [thread overview]
Message-ID: <863chrshay.fsf@trasno.mitica> (raw)
In-Reply-To: <A5974D8E5F98D511BB910002A50A66470B981205@hdsmsx103.hd.intel.com> (Len Brown's message of "Thu, 26 Jun 2003 14:37:11 -0700")
>>>>> "brown," == Brown, Len <len.brown@intel.com> writes:
Hi
brown,> To disable HT on a uni-processor, wouldn't it be preferable to simply run
brown,> the UP kernel rather than the SMP kernel with HT disabled? That leaves SMP
brown,> systems, where either the BIOS could disable it (it is a BIOS bug if it
brown,> can't), or as a last resort CONFIG_X86_HT (2.5) could be config'd out of the
brown,> kernel. I guess I've talked myself into not missing "noht" also.
noht is very useful for distributions, we already have to do a lot of
kernels, any option that "mandates" to compile a different kernel is
just bad (IMHO).
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-06-30 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 21:37 [BK PATCH] acpismp=force fix Brown, Len
2003-06-27 11:58 ` Hugh Dickins
2003-06-27 11:59 ` Arjan van de Ven
2003-06-30 15:42 ` Juan Quintela [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 7:43 Grover, Andrew
2003-06-23 7:58 ` Andrew Morton
2003-06-23 8:01 ` Arjan van de Ven
2003-06-23 11:46 ` Hugh Dickins
2003-06-23 11:54 ` Arjan van de Ven
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=863chrshay.fsf@trasno.mitica \
--to=quintela@trasno.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@digeo.com \
--cc=andrew.grover@intel.com \
--cc=arjanv@redhat.com \
--cc=hugh@veritas.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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