From: Jan Evert van Grootheest <j.grootheest@euronext.nl>
To: "Brown, Len" <len.brown@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
marcelo@parcelfarce.linux.theplanet.co.uk,
Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: HT not working by default since 2.4.22
Date: Fri, 26 Sep 2003 09:44:55 +0200 [thread overview]
Message-ID: <3F73EE77.3000906@euronext.nl> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC8718@hdsmsx402.hd.intel.com>
Len,
I think you're missing Jeffs point.
He's really saying that the user want to select features. The user
doesn't really care how it is implemented. And there is no requirement
(I think) that some source files match one on one with a configuration
option.
As a user I like Jeffs proposal very much. It allows me to indicate what
I want without bothering about the implementation.
I think it would be wise to indicate in the help that HT does include
parts of ACPI.
As a programmer, I can understand your point too. But perhaps you should
do something like this (in the Makefile):
if CONFIG_HT
include part of ACPI needed for HT
endif
if CONFIG_ACPI
include all of acpi
endif
And let make fix things up.
-- Jan Evert
Brown, Len wrote:
>>Now that I've thought of it (aren't I humble), I rather like
>>CONFIG_HT.
>>It's simple and it's effects should be obvious to both developer and
>>user:
>>
>> CONFIG_HT, CONFIG_ACPI == ACPI
>> !CONFIG_HT, CONFIG_ACPI == ACPI
>> CONFIG_HT, !CONFIG_ACPI == HT-only ACPI
>> !CONFIG_HT, !CONFIG_ACPI == no ACPI
>>
>>Following the "autoconf model", what we really want to be testing with
>>CONFIG_xxx is _features_, where possible. "hyperthreading: yes/no" is
>>IMO more clear than "do I want ht-only ACPI or full ACPI",
>>while at the
>>same time being more fine-grained and future-proof.
>
>
> I like positive logic too.
> I went so far as to try to implement this back when I deleted "noht".
>
> The problem is that "!CONFIG_HT" is meaningless. It implies that
> you can have CONFIG_ACPI but still "config-out" HT, which you can't.
>
> Ie. The 2nd row above says to give me ACPI w/o HT.
> If you delete that row and reverse the polarity you get:
>
> !CONFIG_ACPI_HT_ONLY, CONFIG_ACPI == ACPI
> CONFIG_ACPI_HT_ONLY, !CONFIG_ACPI == HT-only ACPI
> !CONFIG_ACPI_HT_ONLY, !CONFIG_ACPI == no ACPI
>
> Here we can use config to emphasize that it is not possible to select
> CONFIG_ACPI and CONFIG_ACPI_HT_ONLY at the same time.
>
> Cheers,
> -Len
>
> Ps. Note that in 2.6 CONFIG_X86_HT exists and covers the sibling code.
> It depends on CONFIG_SMP, and CONFIG_ACPI_HT_ONLY depends on it. (in the
> ACPI patch)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-09-26 7:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 4:54 HT not working by default since 2.4.22 Brown, Len
2003-09-26 7:44 ` Jan Evert van Grootheest [this message]
2003-09-26 17:38 ` Len Brown
2003-09-30 5:27 ` Len Brown
[not found] <BF1FE1855350A0479097B3A0D2A80EE0CC870C@hdsmsx402.hd.intel.com>
2003-09-28 10:43 ` Tomas Szepe
2003-09-28 10:46 ` Tomas Szepe
2003-09-29 1:41 ` Len Brown
2003-09-29 5:29 ` Tomas Szepe
-- strict thread matches above, loose matches on Subject: below --
2003-09-26 1:13 Nakajima, Jun
2003-09-24 21:56 Brown, Len
2003-09-24 23:12 ` Tomas Szepe
2003-09-25 13:33 ` marcelo
2003-09-26 0:04 ` Jeff Garzik
2003-09-26 3:37 ` Len Brown
2003-09-26 3:49 ` Jeff Garzik
2003-09-27 15:26 ` Herbert Poetzl
2003-09-22 17:28 Brown, Len
2003-09-22 17:55 ` Jeff Garzik
2003-09-22 14:41 Nakajima, Jun
2003-09-22 9:00 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=3F73EE77.3000906@euronext.nl \
--to=j.grootheest@euronext.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=jun.nakajima@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=marcelo@parcelfarce.linux.theplanet.co.uk \
/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