linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: option for loading modules into vmalloc area
Date: Wed, 19 Nov 2014 12:12:18 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1411191205530.11690@knanqh.ubzr> (raw)
In-Reply-To: <20141119165948.GM4042@n2100.arm.linux.org.uk>

On Wed, 19 Nov 2014, Russell King - ARM Linux wrote:

> On Wed, Nov 19, 2014 at 11:57:15AM -0500, Nicolas Pitre wrote:
> > On Wed, 19 Nov 2014, Russell King - ARM Linux wrote:
> > > I don't think I ever did, because its pretty much impossible to do as I
> > > explained in a follow up to this thread.
> > > 
> > > We _used_ to do this with the userspace insmod methods, but since we got
> > > this kernel-side linker, it's been pretty much impossible to do without
> > > rewriting the module code.  That's not going to happen on account of one
> > > quirky architecture which Linus doesn't particularly like.
> > 
> > Still... We could try adding a hook in the generic module linker code 
> > for a pre-relocation pass.  Maybe only ARM would use it, but if the need 
> > to load big modules is real then I imagine Linus could be amenable to a 
> > compromise.
> 
> So, how big a table would you allocate for the trampolines, based upon
> not knowing anything about the module being loaded?  4K?  8K?  64K?

The idea of a pre-relocation pass is to determine that.  That could be 
something similar to calling apply_relocate() twice: once to determine 
the number of trampoline entries, and a second time to perform the 
actual relocation.


Nicolas

  reply	other threads:[~2014-11-19 17:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 16:21 [PATCH RFC] ARM: option for loading modules into vmalloc area Konstantin Khlebnikov
2014-11-18 17:34 ` Russell King - ARM Linux
2014-11-18 18:13   ` Konstantin Khlebnikov
2014-11-19 13:40     ` Arnd Bergmann
2014-11-19 14:54       ` Ard Biesheuvel
2014-11-19 15:52         ` Konstantin Khlebnikov
2014-11-19 16:02           ` Ard Biesheuvel
2014-11-19 16:07             ` Russell King - ARM Linux
2014-11-19 16:25               ` Ard Biesheuvel
2014-11-19 16:32                 ` Konstantin Khlebnikov
2014-11-19 16:38                   ` Ard Biesheuvel
2014-11-19 16:55                     ` Russell King - ARM Linux
2014-11-19 16:59                       ` Nicolas Pitre
2014-11-19 16:41                 ` Russell King - ARM Linux
2014-11-19 16:37               ` Nicolas Pitre
2014-11-19 16:41                 ` Ard Biesheuvel
2014-11-19 16:49                 ` Russell King - ARM Linux
2014-11-19 16:57                   ` Nicolas Pitre
2014-11-19 16:59                     ` Russell King - ARM Linux
2014-11-19 17:12                       ` Nicolas Pitre [this message]
2014-11-19 17:59                         ` Ard Biesheuvel
2014-11-19 18:22                           ` Nicolas Pitre

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=alpine.LFD.2.11.1411191205530.11690@knanqh.ubzr \
    --to=nicolas.pitre@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).