public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: davidm@hpl.hp.com
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, bjornw@axis.com,
	geert@linux-m68k.org, ralf@gnu.org, mkp@mkp.net,
	willy@debian.org, anton@samba.org, gniibe@m17n.org,
	kkojima@rr.iij4u.or.jp, Jeff Dike <jdike@karaya.com>
Subject: Re: Userspace Test Framework for module loader porting
Date: Mon, 6 Jan 2003 14:41:04 -0800	[thread overview]
Message-ID: <20030106144104.A1938@twiddle.net> (raw)
In-Reply-To: <15897.56108.201340.229554@napali.hpl.hp.com>; from davidm@napali.hpl.hp.com on Mon, Jan 06, 2003 at 11:38:20AM -0800

On Mon, Jan 06, 2003 at 11:38:20AM -0800, David Mosberger wrote:
> What about all the problems that Richard Henderson pointed out with
> the original in-kernel module loader?  Were those solved?

Yes.  The most important one for correctness was

ChangeSet@1.838.130.13, 2003-01-01 19:02:38-08:00, rusty@rustcorp.com.au
  [PATCH] Modules 3/3: Sort sections
  
  RTH's final complaint (so far 8) was that we should sort the module
  sections: archs might require some sections to be adjacent, so they can
  all be reached by a relative pointer (ie.  GOT pointer).  This
  implements that reordering, and simplfies the module interface for
  architectures as well.
  
  Previously an arch could specify it wanted extra space, but not where
  that space would be.  The new method (used only by PPC so far) is to
  allocate an empty section (in asm/module.h or by setting LDFLAGS_MODULE
  to use an arch specific linker script), and expand that to the desired
  size in "module_frob_arch_sections()".


> My gut feeling is that we really want shared objects for kernel
> modules on ia64 (and probably alpha?).

Well, most everyone wants it.  Except that MIPS is terminally
broken.  They need a rewrite of bfd/elfxx-mips.c in order to
be able to do non-pic ET_DYN images.  Which leaves the rest of
us out in the cold.


r~

  reply	other threads:[~2003-01-06 22:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06  2:27 Userspace Test Framework for module loader porting Rusty Russell
2003-01-06 19:38 ` David Mosberger
2003-01-06 22:41   ` Richard Henderson [this message]
2003-01-07  0:37     ` David Mosberger
2003-01-08 11:44       ` Rusty Russell
2003-01-11  1:47         ` David Mosberger
2003-01-13  0:27           ` Rusty Russell
2003-01-13 13:20             ` Maciej W. Rozycki
2003-01-14  0:01               ` Rusty Russell
2003-01-24 18:23                 ` return-type for search_extable() David Mosberger
2003-01-28  4:53                   ` Rusty Russell
2003-01-28  6:14                     ` David Mosberger
2003-01-08 11:21   ` Userspace Test Framework for module loader porting Rusty Russell

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=20030106144104.A1938@twiddle.net \
    --to=rth@twiddle.net \
    --cc=anton@samba.org \
    --cc=bjornw@axis.com \
    --cc=davidm@hpl.hp.com \
    --cc=geert@linux-m68k.org \
    --cc=gniibe@m17n.org \
    --cc=jdike@karaya.com \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkp@mkp.net \
    --cc=ralf@gnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=willy@debian.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