From: Willy Tarreau <willy@w.ods.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Len Brown <len.brown@intel.com>,
Arkadiusz Miskiewicz <arekm@pld-linux.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: Linux 2.4.26-rc1 (cmpxchg vs 80386 build)
Date: Tue, 30 Mar 2004 16:22:15 +0200 [thread overview]
Message-ID: <20040330142215.GA21931@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.53.0403300814350.5311@chaos>
On Tue, Mar 30, 2004 at 08:15:46AM -0500, Richard B. Johnson wrote:
> On Tue, 30 Mar 2004, Alan Cox wrote:
>
> > On Llu, 2004-03-29 at 23:07, Len Brown wrote:
> > > Linux uses this locking mechanism to coordinate shared access
> > > to hardware registers with embedded controllers,
> > > which is true also on uniprocessors too.
> >
> > If the ACPI layer simply refuses to run on a CPU without cmpxchg
> > then I can't see there being a problem, there don't appear to be
> > any 386 processors with ACPI
> >
>
> Yep, but to get to use cmpxchg, you need to compile as a '486 or
> higher. This breaks i386.
OK, so why not compile the cmpxchg instruction even on i386 targets
to let generic kernels stay compatible with everything, but disable
ACPI at boot if the processor does not feature cmpxchg ? This could
be helpful for boot/install kernels which try to support a wide
range of platforms, and may need ACPI to correctly enable interrupts
on others.
Cheers,
Willy
next prev parent reply other threads:[~2004-03-30 14:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F6939@hdsmsx402.hd.intel.com>
2004-03-29 4:49 ` Linux 2.4.26-rc1 (cmpxchg vs 80386 build) Len Brown
2004-03-29 0:09 ` [ACPI] " Andi Kleen
2004-03-29 5:22 ` Willy Tarreau
2004-03-29 7:01 ` Denis Vlasenko
2004-03-29 19:57 ` Willy Tarreau
2004-03-29 22:07 ` Len Brown
2004-03-30 12:56 ` [ACPI] " Alan Cox
2004-03-30 13:15 ` Richard B. Johnson
2004-03-30 14:22 ` Willy Tarreau [this message]
2004-03-30 14:48 ` Richard B. Johnson
2004-03-30 15:09 ` Willy Tarreau
2004-03-30 15:33 ` Richard B. Johnson
2004-03-30 16:14 ` Willy Tarreau
2004-03-30 16:42 ` Chris Friesen
2004-03-30 17:44 ` Len Brown
2004-03-30 18:30 ` Arkadiusz Miskiewicz
2004-03-30 20:05 ` Len Brown
2004-03-30 20:25 ` Arkadiusz Miskiewicz
2004-03-30 21:49 ` Len Brown
2004-03-30 20:08 ` Bill Davidsen
2004-03-31 11:13 ` Maciej W. Rozycki
2004-03-31 13:04 ` Bill Davidsen
2004-03-31 15:02 ` Jamie Lokier
2004-04-01 12:29 ` Maciej W. Rozycki
2004-04-01 13:17 ` Richard B. Johnson
2004-05-08 10:18 ` Denis Vlasenko
2004-04-01 20:46 ` Len Brown
2004-04-02 10:54 ` Maciej W. Rozycki
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=20040330142215.GA21931@alpha.home.local \
--to=willy@w.ods.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arekm@pld-linux.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=root@chaos.analogic.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