From: Arkadiusz Miskiewicz <arekm-k0Z414SquRyhPH1hqNUYSQ@public.gmane.org>
To: Denis Vlasenko
<vda-so6tiL4DrmS23Ynj82S0jdyBExgiH1vWcG62WxB9dV4@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Linux 2.4.26-rc1 (cmpxchg vs 80386 build)
Date: Mon, 29 Mar 2004 11:56:38 +0200 [thread overview]
Message-ID: <200403291156.38961.arekm@pld-linux.org> (raw)
In-Reply-To: <200403290901.47695.vda-so6tiL4DrmS23Ynj82S0jdyBExgiH1vWcG62WxB9dV4@public.gmane.org>
Dnia Monday 29 of March 2004 09:01, Denis Vlasenko napisał:
> > > 4. re-implement locks for the 80386 case.
> >
> > I like this one, but a simpler way : don't support SMP in this case, so
> > that we won't have to play with locks. This would lead to something like
> > this :
>
> Yes, SMP makes sense only on 486+
I want to run i386 compiled kernel on 486+ smp machines
> > #ifndef CONFIG_X86_CMPXCHG
> > #ifndef CONFIG_SMP
> > #define cmpxchg(lock,old,new) ((*lock == old) ? ((*lock = new), old) :
> > (*lock)) #else
> > #define cmpxchg(lock,old,new) This_System_Is_Not_Supported
> > #endif
> > #endif
and this won't allow me to do that
> > This code (if valid) might be added to asm-i386/system.h so that we don't
> > touch ACPI code.
> >
> > Any comments ?
so I preffer 3. invoke cmpxchg from acpi even for 80386 build + cpuid/other
check to not run this code on 386.
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
next prev parent reply other threads:[~2004-03-29 9:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F6939@hdsmsx402.hd.intel.com>
[not found] ` <A6974D8E5F98D511BB910002A50A6647615F6939-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-03-29 4:49 ` Linux 2.4.26-rc1 (cmpxchg vs 80386 build) Len Brown
[not found] ` <1080535754.16221.188.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-29 0:09 ` Andi Kleen
2004-03-29 5:22 ` Willy Tarreau
2004-03-29 7:01 ` Denis Vlasenko
[not found] ` <200403290901.47695.vda-so6tiL4DrmS23Ynj82S0jdyBExgiH1vWcG62WxB9dV4@public.gmane.org>
2004-03-29 9:56 ` Arkadiusz Miskiewicz [this message]
[not found] ` <200403291156.38961.arekm-k0Z414SquRyhPH1hqNUYSQ@public.gmane.org>
2004-03-29 11:31 ` Alan Cox
2004-03-29 19:57 ` Willy Tarreau
[not found] ` <20040329052238.GD1276-HkMpAodKYdnXX8ko2wsARw@public.gmane.org>
2004-03-29 11:05 ` Frank Mehnert
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
2004-03-30 14:48 ` Richard B. Johnson
2004-03-30 15:09 ` Willy Tarreau
[not found] ` <20040330150949.GA22073-HkMpAodKYdnXX8ko2wsARw@public.gmane.org>
2004-03-30 15:33 ` Richard B. Johnson
2004-03-30 16:14 ` [ACPI] " Willy Tarreau
2004-03-30 16:42 ` Chris Friesen
[not found] ` <4069A359.7040908-hwFIcccggHZv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2004-03-30 17:44 ` Len Brown
2004-03-30 18:30 ` [ACPI] " 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
[not found] ` <4069D3D2.2020402-sQDSfeB7uhw@public.gmane.org>
2004-03-31 11:13 ` Maciej W. Rozycki
2004-03-31 13:04 ` [ACPI] " 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
[not found] ` <Pine.LNX.4.55.0404011423070.3675-rsPqkUlH4Vdx0R2ya2r/wqsMm+1xrEX8@public.gmane.org>
2004-04-01 20:46 ` Len Brown
[not found] ` <1080852371.30349.19.camel-D2Zvc0uNKG8@public.gmane.org>
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=200403291156.38961.arekm@pld-linux.org \
--to=arekm-k0z414squryhph1hqnuysq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=vda-so6tiL4DrmS23Ynj82S0jdyBExgiH1vWcG62WxB9dV4@public.gmane.org \
/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