Re: Hyper-threaded pickle

[Len Brown]

> > Re: old systems -- we use dmi_scan to disable ACPI on systems by default
> > on systems older than 1/1/2001.
> 
> What happens for the no-DMI case?

When DMI is not present, dmi_scan is a no-op -- so ACPI will run in
whatever default the system is set to -- eg. "off" for FC1, and "on" for
FC2-test1.

We've found in practice that dmi_scan has been pretty effective at
identifying the set of systems new enough to have an ACPI enabled BIOS
but old enough that the ACPI implementation is hopeless.  Though we've
had many reports of 1/1/2001 being a bit *too* conservative -- disabling
ACPI on systems where ACPI works fine.  Indeed, there is a bugzilla
requesting a "white-list" to enable exceptions to this date.  I'm not
enthusiastic about that plan, however.  I figure there are more 3-year
old boxes that have been running Linux w/o ACPI than there are those
which have; and I'd rather spend my ergs on the current and upcoming
boxes where vendors are more willing to update a broken BIOS...

> > Re: opteron & !HT.  Andi showed me a patch today that disables X86_HT if
> > you build specifically for an AMD CPU that doesn't support HT.  This
> > looks like a good idea, and possibly should be expanded.
> 
> Cool.
> 
> My main worry/concern is breaking older systems, due to this change in 
> behavior.

2.4 and SuSE have deployed this way for some time.  The HT part of ACPI
was in RHL 8.0 and 9.0 by default as well -- and this is consistent with
that.

> An easy first step is to make CONFIG_X86_HT selectable again.

That wouldn't help the most importaht case though -- the distro who
wants the same kernel binary to run on a broad variety of platforms.

-Len


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/