linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brown, Len" <len.brown@intel.com>
To: "Marcelo Tosatti" <marcelo.tosatti@cyclades.com.br>
Cc: <linux-kernel@vger.kernel.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Jeff Garzik" <jgarzik@pobox.com>
Subject: RE: HT not working by default since 2.4.22
Date: Wed, 24 Sep 2003 17:56:57 -0400	[thread overview]
Message-ID: <BF1FE1855350A0479097B3A0D2A80EE0CC8708@hdsmsx402.hd.intel.com> (raw)

Okay, so what to do?

We could make 2.4.23 like 2.4.21 where ACPI code for HT is included in
the kernel even when CONFIG_ACPI is not set.

Or we could leave 2.4.23 like 2.4.22 where disabling CONFIG_ACPI really
does remove all ACPI code in the kernel; and when CONFIG_ACPI is set,
CONFIG_ACPI_HT_ONLY is available to limit ACPI to just the tables part
needed for HT.

I'd prefer the later (doing nothing) because CONFIG_ACPI really should
exclude all of ACPI.  If we start including bits of ACPI without
CONFIG_ACPI, where do we stop?

I'm not sure how to address "compatibility" and "regression" concepts in
the face of changing config files.  Make oldconfig will ask you about
CONFIG_ACPI -- perhaps I should update the help text to emphasize that
it is necessary for HT, and that if selected, CONFIG_ACPI_HT_ONLY is
then available?

Is defconfig used?  Does it define "compatibility"?  If so, we could
define CONFIG_ACPI && CONFIG_ACPI_HT_ONLY in defconfig to get the 2.4.21
behavior -- then could have our cake and eat it too.

I don't feel strongly about which way to go, but I will want to keep 2.4
and 2.6 as similar as possible in this area.

Thanks,
-Len


> -----Original Message-----
> From: Jeff Garzik [mailto:jgarzik@pobox.com] 
> Sent: Monday, September 22, 2003 1:55 PM
> To: Brown, Len
> Cc: Marcelo Tosatti; linux-kernel@vger.kernel.org; Alan Cox; 
> Nakajima, Jun
> Subject: Re: HT not working by default since 2.4.22
> 
> 
> On Mon, Sep 22, 2003 at 01:28:03PM -0400, Brown, Len wrote:
> > If somebody has a 2.4.22 system where CONFIG_ACPI_HT_ONLY plus zero
> > cmdline parameters doesn't result in HT running and no ACPI running,
> > then please forward the details directly to me.
> 
> The old acpitable.[ch] was unconditionally enabled...  So _not_
> unconditionally enabling HT was a regression.
> 
> (just pointing out a fact;  I actually prefer a CONFIG_xxx)
> 
> 	Jeff
> 
> 
> 
> 

             reply	other threads:[~2003-09-24 21:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 21:56 Brown, Len [this message]
2003-09-24 23:12 ` HT not working by default since 2.4.22 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
     [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  4:54 Brown, Len
2003-09-26  7:44 ` Jan Evert van Grootheest
2003-09-26 17:38   ` Len Brown
2003-09-30  5:27   ` Len Brown
2003-09-26  1:13 Nakajima, Jun
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=BF1FE1855350A0479097B3A0D2A80EE0CC8708@hdsmsx402.hd.intel.com \
    --to=len.brown@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).