From: jlnance@intrex.net
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: modules and 2.5
Date: Tue, 3 Jul 2001 08:15:15 -0400 [thread overview]
Message-ID: <20010703081515.B1146@bessie.localdomain> (raw)
In-Reply-To: <3B415489.77425364@mandrakesoft.com>
In-Reply-To: <3B415489.77425364@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Jul 03, 2001 at 01:13:45AM -0400
On Tue, Jul 03, 2001 at 01:13:45AM -0400, Jeff Garzik wrote:
> A couple things that would be nice for 2.5 is
> - let MOD_INC_USE_COUNT work even when module is built into kernel, and
> - let THIS_MODULE exist and be valid even when module is built into
> kernel
I have something similar that I have wanted for a long time, and it would
accomplish what you want too. I would like for the .o files for modules and
compiled in drivers to be identical. It seems like this would be better for
testing because it should eleminate module vs non-module bugs. We might
even want them to show up in /proc/modules, perhaps with some mechinism to
keep the reference count from going to 0.
I dont think I would want to unleash it on an end user, but if you omit the
part about letting the reference count go to zero, it should even be possible
to unload a compiled in driver and replace it with a new module. If you
did not load each module into its own section, you would have to leak its
text and data memory, but this still might be useful for development.
Anyway, just some ideas I have been wanting to share for about 5 years.
Thanks for giving me an excuse.
Jim
next prev parent reply other threads:[~2001-07-03 12:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 5:13 Jeff Garzik
2001-07-03 6:50 ` Sean Hunter
2001-07-03 7:05 ` Jeff Garzik
2001-07-03 7:16 ` Keith Owens
2001-07-03 7:24 ` Jeff Garzik
2001-07-03 7:39 ` Keith Owens
2001-07-03 7:44 ` Jeff Garzik
2001-07-03 7:48 ` Fang Han
2001-07-03 7:18 ` Keith Owens
2001-07-03 12:15 ` jlnance [this message]
2001-07-06 10:34 ` Rusty Russell
2001-07-07 14:12 ` Jeff Garzik
2001-07-08 7:40 ` Rusty Russell
2001-07-11 22:04 ` Pavel Machek
2001-07-03 17:35 Andrzej Krzysztofowicz
2001-07-03 17:39 ` Jeff Garzik
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=20010703081515.B1146@bessie.localdomain \
--to=jlnance@intrex.net \
--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 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®