From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions
Date: Fri, 02 May 2008 16:38:55 -0700 (PDT) [thread overview]
Message-ID: <20080502.163855.96423898.davem@davemloft.net> (raw)
In-Reply-To: <1209770875.26383.14.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Sat, 03 May 2008 09:27:55 +1000
> That is, it would be fairly non-sensical for module code to go through
> the trampoline to call those stubs in the kernel (and having to
> EXPORT_SYMBOL them).
Oh, I forgot about how far function calls are done on powerpc.
Yes, that will suck.
Is there some way to map all of the modules in the low 32-bits and
thus aovid the trampolines? The powerpc call instruction can cover
4GB like on sparc right?
Actually, I remember there is some linkage register that has
to be setup on powerpc with the code model you guys use, is
that the problem?
next prev parent reply other threads:[~2008-05-02 23:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 8:11 [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions Kumar Gala
2008-05-02 11:54 ` Segher Boessenkool
2008-05-02 13:28 ` Kumar Gala
2008-05-02 13:37 ` Segher Boessenkool
2008-05-02 13:41 ` Kumar Gala
2008-05-02 15:20 ` Scott Wood
2008-05-02 17:15 ` Segher Boessenkool
2008-05-02 14:09 ` Kumar Gala
2008-05-02 17:11 ` Segher Boessenkool
2008-05-02 21:28 ` Kumar Gala
2008-05-02 21:40 ` David Miller
2008-05-02 21:58 ` Kumar Gala
2008-05-02 23:27 ` Benjamin Herrenschmidt
2008-05-02 23:38 ` David Miller [this message]
2008-05-03 0:06 ` Segher Boessenkool
2008-05-03 7:50 ` Benjamin Herrenschmidt
2008-05-03 7:55 ` David Miller
2008-05-03 11:01 ` Benjamin Herrenschmidt
2008-05-05 11:55 ` Gabriel Paubert
2008-05-02 12:13 ` Josh Boyer
2008-05-02 13:32 ` Kumar Gala
2008-05-02 13:53 ` Josh Boyer
2008-05-02 13:59 ` Kumar Gala
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=20080502.163855.96423898.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).