From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [PATCH]Modules support in 2.6: reaching the complete fix
Date: Sun, 14 Dec 2003 16:04:32 +0100 [thread overview]
Message-ID: <200312141604.32309.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200312132019.hBDKJ8rL002905@ccure.user-mode-linux.org>
First, I tried without CONFIG_MODVERSIONS, and the panic doesn't happen(which
was obvious, since the offending code is compiled #ifdef MODVERSIONS) and no
other one appears. And the module loading works.
Only thing which obviously can't work is the umlgdb script; I need 2.6 Uml
modules because I need to test a change to the 2.6 loop device(i.e. the
partition support).
[About user_ksyms.c]
> Yeah, this is nasty, but I couldn't think of any way of handling this
> without just copying stuff.
Yes, I understand you've tried(though I don't know why user code can't include
even some kernel headers, but that's my fault).
> > 2) then, the UML build system is broken for USER_OBJS.
>
> This is separate from the module problem. It still needs fixing though.
Yes, but the general rule does some post-processing which is needed for
modules. See scripts/Makefile.build:134 and following ones(around the
"cmd_modversions" definition).
>
> It would be nice just to have something in one Makefile, like
> arch/um/Makefile, which makes this work. I haven't looked at whether this
> is possible.
I'm going to try!
> > And for this, I cannot help because I've not enough experience with
> > link scripts(I've been able to learn the syntax, but I don't know the
> > reason why some section missing in the i386 appear in the UML script;
> > some are from libc, but I don't know which ones).
>
> The ones you deleted are all kernel sections.
I understand this well(I'm aware of how are they born), but check and see that
the RODATA macro, know, already includes them... so it's useless(if not
harmful, but it shouldn't) to list them twice.
Bye
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-12-14 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 17:28 [uml-devel] [PATCH]Modules support in 2.6: reaching the complete fix BlaisorBlade
2003-12-13 20:19 ` [uml-devel] " Jeff Dike
2003-12-14 15:04 ` BlaisorBlade [this message]
2003-12-17 17:51 ` BlaisorBlade
2003-12-18 1:19 ` Jeff Dike
2003-12-18 19:32 ` BlaisorBlade
2003-12-18 22:13 ` Jeff Dike
2003-12-19 19:51 ` BlaisorBlade
2003-12-23 19:31 ` BlaisorBlade
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=200312141604.32309.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.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