From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: relocation out of range (when loading a module)
Date: Wed, 12 Jan 2011 10:05:19 -0600 [thread overview]
Message-ID: <AANLkTimAFp7ORrJLw2d8-i5pK0MZGTyAN5kmRR37ky1v@mail.gmail.com> (raw)
In-Reply-To: <4D2D1942.4050905@ahsoftware.de>
On Tue, Jan 11, 2011 at 9:00 PM, Alexander Holler <holler@ahsoftware.de> wrote:
> Hello,
[...]
> ? ? ? ? ? ? ? ?INIT_CALLS
> ? ? ? ? ? ? ? ?CON_INITCALL
> ? ? ? ? ? ? ? ?SECURITY_INITCALL
> + ? ? ? ? ? ? ? /*
> + ? ? ? ? ? ? ? ?* TODO: The size of INIT_RAM_FS could easily reach a
> + ? ? ? ? ? ? ? ?* point (~16MB) when loading modules will fail because
> + ? ? ? ? ? ? ? ?* relocations will be out of range. So this place here
> + ? ? ? ? ? ? ? ?* isn't the best one.
> + ? ? ? ? ? ? ? ?*/
> ? ? ? ? ? ? ? ?INIT_RAM_FS
In general, do we expect always to be able to avoid the situation
where branches in the kernel may need to cover too large a range ...
and is there any strategy for working aroung it?
If we have problems branching from the modules area into vmlinux, we
could possibly build modules with -fPIC : this would remove the
restriction on branch range, though there would also be some
performance impact for the modules...
Cheers
---Dave
next prev parent reply other threads:[~2011-01-12 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2B4CE4.9080309@ahsoftware.de>
[not found] ` <alpine.LFD.2.00.1101101722470.9794@xanadu.home>
[not found] ` <4D2BFA08.5030104@ahsoftware.de>
2011-01-11 15:46 ` ARM: relocation out of range (when loading a module) Rabin Vincent
2011-01-11 15:59 ` Russell King - ARM Linux
2011-01-12 3:00 ` Alexander Holler
2011-01-12 16:05 ` Dave Martin [this message]
2011-01-12 16:23 ` Russell King - ARM Linux
2011-01-12 18:28 ` Nicolas Pitre
2011-01-12 18:42 ` Russell King - ARM Linux
2011-01-12 18:55 ` Nicolas Pitre
2011-01-25 8:44 ` Sachin Verma
2011-01-25 13:23 ` Catalin Marinas
2011-01-27 5:43 ` Nicolas Pitre
2011-02-10 15:43 ` Russell King - ARM Linux
2011-02-10 19:41 ` Nicolas Pitre
2011-02-11 9:31 ` Dave Martin
2011-02-11 9:38 ` Russell King - ARM Linux
2011-02-11 9:45 ` Dave Martin
2011-02-11 13:55 ` Nicolas Pitre
2011-02-11 13:51 ` Nicolas Pitre
2011-02-11 14:25 ` Dave Martin
2011-02-11 14:42 ` Russell King - ARM Linux
2011-02-12 19:52 ` Nicolas Pitre
2011-01-13 5:50 ` Alexander Holler
2011-01-13 10:04 ` Russell King - ARM Linux
2011-01-13 14:36 ` Alexander Holler
2011-01-12 16:25 ` Matthieu CASTET
2011-01-12 16:38 ` Russell King - ARM Linux
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=AANLkTimAFp7ORrJLw2d8-i5pK0MZGTyAN5kmRR37ky1v@mail.gmail.com \
--to=dave.martin@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).