From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Unify module.*
Date: Mon, 22 Dec 2008 22:07:45 +0000 [thread overview]
Message-ID: <20081222220745.GA30716@uranus.ravnborg.org> (raw)
Following patchset unifies module.h and module.c.
The unification is done in a few smaller steps to make
it obvious what is happeing.
The first two patches unify module.h and prepare for
unification of module.c.
The third and fourth patch do all the preparations of module_64.c
without introducing any sparc32 specific code but all
sparc64 specific code is ifdef'ed.
I really did not like this part:
#ifdef CONFIG_SPARC64
BUG_ON(((u64)location >> (u64)32) != (u64)0);
#endif /* CONFIG_SPARC64 */
I think it should be safe to do:
BUG_ON(((unsigned long)location >> (unsigned long)32) ! (unsigned long)0);
As to my best understanding unsigned long
is 32 bit on sparc32 and 64 bit on sparc64.
So we should with the above code not get any warnings.
But I did not really see the point of the BUG_ON in the first place,
and my limited digging did not turn up when it was added.
So to be safe I kept the ugly ifdef for now.
If is easy to spot/remove.
The final patch that unifies module.c adds one specific entry
to the case that is sparc32 specific:
case R_SPARC_32:
+ case R_SPARC_UA32:
But this should not cause any problems.
The patch serie is build tested on a defconfig for
sparc and sparc64.
Sam
Sam Ravnborg (5):
sparc: introduce CONFIG_BITS
sparc: unify module.h
sparc64: use bit neutral Elf symbols
sparc64: prepare module_64.c for unification
sparc: unify module.c
arch/sparc/Kconfig | 6 +-
arch/sparc/include/asm/module.h | 32 ++++--
arch/sparc/include/asm/module_32.h | 7 -
arch/sparc/include/asm/module_64.h | 7 -
arch/sparc/kernel/Makefile | 2 +-
arch/sparc/kernel/{module_64.c => module.c} | 112 +++++++++++++------
arch/sparc/kernel/module_32.c | 163 ---------------------------
7 files changed, 107 insertions(+), 222 deletions(-)
next reply other threads:[~2008-12-22 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 22:07 Sam Ravnborg [this message]
2008-12-22 22:31 ` Unify module.* Sam Ravnborg
2008-12-22 22:34 ` Chris Torek
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=20081222220745.GA30716@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.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 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.