From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] xchg/cmpxchg defined in wrong place?
Date: Sat, 30 Dec 2000 17:55:41 -0800 [thread overview]
Message-ID: <200012310155.RAA25264@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Sat, 30 Dec 2000 09:52:49 PST." <200012301752.JAA25055@milano.cup.hp.com>
Grant Grundler wrote:
> ok. I'll take a whack at parisc arch and see what happens.
This was easy. Was even able to build/link with DRM and all the
related drivers. Code change committed to parisc-linux CVS:
o removes bogus definition of __xchg_called_with_bad_pointer from setup.c
o definitions follow sparc64 model except I didn't try to inline all
of this mess.
o added __xchgNN() and __cmpxchg_uNN() functions to bitops.c and
declared them in parisc_ksyms.c for CONFIG_MODULES support.
o added "include <asm/atomic.h>" to arch/parisc/kernel/semaphore.c
to make sure it gets the xchg() macro definition.
TODO: DRM should explicitly include asm/atomic.h to pick up
#define __HAVE_ARCH_CMPXCHG directly.
> If it's easy, I'll try the i386 arch as well - mostly
> to build more drivers as a sanity check.
I moved all the xchg/cmpxchg related code from include/asm-i386/system.h
to include/asm-i386/atomic.h and built an x86 kernel (natively) but didn't
boot it. Booting the kernel shouldn't be necessary since mis-use will
result in a linker error (xchg undefined).
I used 2.4.0-test10 since it was handy. Once I get newer Linus
tree, I can cut/paste again and submit the patch to l-k.
Should be able to do this in the next couple of days unless someone
tells me they've done it already.
thanks,
grant
next prev parent reply other threads:[~2000-12-31 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 5:12 [parisc-linux] xchg/cmpxchg defined in wrong place? Grant Grundler
2000-12-30 6:41 ` Grant Grundler
2000-12-30 16:46 ` Alan Cox
2000-12-30 17:52 ` Grant Grundler
2000-12-31 1:55 ` Grant Grundler [this message]
2000-12-31 4:16 ` R P Herrold
2001-01-02 0:09 ` Dual Boot Grant Grundler
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=200012310155.RAA25264@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.