Messages in this thread |  | | Date | Sun, 26 Nov 2000 20:27:00 -0700 | From | "Jeff V. Merkey" <> | Subject | Re: initdata for modules? |
| |
On Mon, Nov 27, 2000 at 01:06:04PM +1100, Keith Owens wrote: > 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.
:-)
Jeff
- 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/
|  |