From: Keith Owens <kaos@ocs.com.au>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: initdata for modules?
Date: Mon, 27 Nov 2000 13:06:04 +1100 [thread overview]
Message-ID: <3478.975290764@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 26 Nov 2000 19:49:43 PDT." <20001126194943.F2265@vger.timpanogas.org>
On Sun, 26 Nov 2000 19:49:43 -0700,
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org> wrote:
>Microsoft drivers have an .INIT code section that is initialization
>ccode that get's chunked after it's loaded. Their model allows
>memory segments to be defined as DISCARDABLE, which tells the loader
>to chunk them after they get loaded in portable executable format.
The loader is insmod, which does all its own reloaction and loading.
The problem is that ancillary tools like ksymoops, gdb, kdb and
possibly others do not expect sections to be discarded after load.
Adding the feature to insmod is fairly easy, fixing the ancillary tools
to understand that some sections are discarded after load is a bit
harder. Debugging is particularly messy, when an oops occurs how do we
tell if the __init data been discarded yet or not?
I have added this to my investigation list for modutils, ksymoops and
kdb 2.5, no promises.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-27 2:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 23:47 initdata for modules? Adam J. Richter
2000-11-27 2:49 ` Jeff V. Merkey
2000-11-27 2:06 ` Keith Owens [this message]
2000-11-27 3:27 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2000-11-26 15:30 Adam J. Richter
2000-11-26 22:54 ` Keith Owens
2000-11-27 0:01 ` Jeff V. Merkey
2000-11-26 23:45 ` Keith Owens
2000-11-27 2:45 ` Jeff V. Merkey
2000-11-27 7:35 ` Jakub Jelinek
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=3478.975290764@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=adam@yggdrasil.com \
--cc=jmerkey@vger.timpanogas.org \
--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