From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Query about initramfs and modules
Date: 16 Jan 2002 10:13:55 -0800 [thread overview]
Message-ID: <a24ft3$4au$1@cesium.transmeta.com> (raw)
In-Reply-To: <15428.47094.435181.278715@irving.iisd.sra.com> <a22nc0$2fh$1@cesium.transmeta.com> <15429.48638.96256.842851@irving.iisd.sra.com>
Followup to: <15429.48638.96256.842851@irving.iisd.sra.com>
By author: David Garfield <garfield@irving.iisd.sra.com>
In newsgroup: linux.dev.kernel
>
> Agreed. However, this work could easily be performed by an insmod
> variant that takes a module, a "System.map", and a kernel image, and
> produces a cpio file as output instead of passing the data to the
> kernel for immediate processing. The kernel mechanism would then only
> need to unpack the pieces, relocate, and make the system calls.
>
How do you know where the running kernel will be allocating address
space for the module?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-16 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 23:15 Query about initramfs and modules David Garfield
2002-01-15 23:34 ` Greg KH
2002-01-15 23:47 ` David Garfield
2002-01-16 0:01 ` Greg KH
2002-01-16 0:33 ` David Garfield
2002-01-16 1:16 ` Greg KH
2002-01-16 19:29 ` Andreas Ferber
2002-01-16 19:40 ` Greg KH
2002-01-16 19:53 ` Jordan Crouse
2002-01-16 2:09 ` H. Peter Anvin
2002-01-16 17:53 ` David Garfield
2002-01-16 18:13 ` H. Peter Anvin [this message]
2002-01-16 19:04 ` David Garfield
2002-01-16 3:29 ` Alexander Viro
2002-01-16 19:41 ` Erik Andersen
2002-01-16 19:56 ` H. Peter Anvin
2002-01-16 20:18 ` Erik Andersen
2002-01-16 20:23 ` H. Peter Anvin
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='a24ft3$4au$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.