From: Rusty Russell <rusty@rustcorp.com.au>
To: Richard Henderson <rth@twiddle.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modules as shared objects
Date: Mon, 25 Nov 2002 12:10:50 +1100 [thread overview]
Message-ID: <20021125011223.74AC82C0F3@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 23 Nov 2002 14:01:28 -0800." <20021123140128.A699@twiddle.net>
In message <20021123140128.A699@twiddle.net> you write:
> * Freeing the .init.* sections. Also requires the link script.
> I believe the proper solution is to use a different program
> header with a different load tag:
>
> #define PT_INIT_LOAD 0x60000001
>
> In this way we don't make a mistake and discard a segment that
> we're not supposed to.
Were you thinking of dropping the dynamic at the same time
(ie. putting the dynamic and init sections in the tail using the
linker script)? Hmm, I guess not since you
I think an "mod_arch_free_partial(struct module *mod, void *start,
void *end)" function which archs could use to do whatever fancy magic
they wanted (eg. trim exception and really drop the pages, or your
vmalloc_drop_pages() function, or nothing at all). x86_64, sparc,
sparc64, ppc and arm do/will have their own allocators already.
> +module_core_size(const ElfW(Ehdr) *hdr, struct module *module,
I *really* hate this ElfW(type) notation. I know it's used in
binutils etc, but it's a visual bitch to parse. Please please please
at least use the #defines or typedefs within the generic
kernel/module.c so it's readable.
Other than some gratuitous reformatting 8), looks really good.
Implementing PPC now.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-25 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 22:01 Richard Henderson
2002-11-25 1:10 ` Rusty Russell [this message]
2002-11-24 1:16 Adam J. Richter
2002-11-24 4:36 ` Richard Henderson
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=20021125011223.74AC82C0F3@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®