linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: relocation out of range (when loading a module)
Date: Fri, 11 Feb 2011 09:38:53 +0000	[thread overview]
Message-ID: <20110211093853.GA23404@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=KtFf5BU-iH-sUUL=Q30S90bk608JR4zFz2CKf@mail.gmail.com>

On Fri, Feb 11, 2011 at 09:31:04AM +0000, Dave Martin wrote:
> You could probably cook up a good upper bound based on the size of the
> kernel and the number of symbols in the module: i.e., assume that
> every undefined symbol in the module needs to be fixed up to point at
> the most distant symbol in the kernel.
> 
> For people with normal-sized kernels, this bound will probably work
> out as zero most of the time (i.e., the current situation).  For
> people with big kernels, or when many modules are already loaded, it
> may work out at 100% -- but that's the price to pay for guaranteed
> preallocation of the space required for the veneers.  And anyway, you
> may really need a substantial chunk of those veneers in such cases.

I think it's going to be easier just to re-order the kernel image link
order to solve that problem.  That just leaves uclinux...

  reply	other threads:[~2011-02-11  9:38 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
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 [this message]
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=20110211093853.GA23404@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).