From: Rusty Russell <rusty@rustcorp.com.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Module loader against 2.5.46: 9/9
Date: Sat, 09 Nov 2002 14:01:22 +1100 [thread overview]
Message-ID: <20021109041543.D3F902C283@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 08 Nov 2002 09:35:16 -0000." <20021108093516.A15440@flint.arm.linux.org.uk>
In message <20021108093516.A15440@flint.arm.linux.org.uk> you write:
> On Thu, Nov 07, 2002 at 10:08:24PM +1100, Rusty Russell wrote:
> > That explains it: I didn't think you were insane 8). Thanks, I'll
> > move it to some other name which just does the "add symbols to oops"
> > minimum.
>
> I doubt that we need all of the kallsyms data in the kernel as well (unless
> you're using kdb.)
Yes. From my IDE oops dumper experience, you can get the required
kernel symbols down to 70k w/o kdb (it's about 380k as stands). I
haven't made this optimization yet though.
> One of the things on my todo list is to look into a kallsyms replacement
> that allows cross-compilation (and actually allows kallsyms to work at
> all on ARM.)
>
> ARM requires the ELF architecture private flags to be set correctly to link
> two objects together. So there's two problems with the current setup:
Hmm, depends on state of module loader code. If it goes in, you'll
be getting a new one anyway which doesn't have this problem (I use $CC
to create kallsyms.o which gets linked in). Otherwise, yes.
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2002-11-09 4:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 0:21 [PATCH] Module loader against 2.5.46: 1/9 Rusty Russell
2002-11-05 0:29 ` [PATCH] Module loader against 2.5.46: 3/9 Rusty Russell
2002-11-05 0:31 ` [PATCH] Module loader against 2.5.46: 4/9 Rusty Russell
2002-11-05 0:35 ` [PATCH] Module loader against 2.5.46: 5/9 Rusty Russell
2002-11-05 0:36 ` [PATCH] Module loader against 2.5.46: 6/9 Rusty Russell
2002-11-05 0:41 ` [PATCH] Module loader against 2.5.46: 7/9 Rusty Russell
2002-11-05 0:43 ` [PATCH] Module loader against 2.5.46: 8/9 Rusty Russell
2002-11-05 3:19 ` Werner Almesberger
2002-11-05 3:51 ` Rusty Russell
2002-11-05 4:08 ` Werner Almesberger
2002-11-05 4:24 ` Rusty Russell
2002-11-06 16:45 ` Bill Davidsen
2002-11-07 11:24 ` Rusty Russell
2002-11-08 3:15 ` Randy.Dunlap
2002-11-08 21:15 ` Bill Davidsen
2002-11-09 12:24 ` Mark H. Wood
2002-11-10 3:21 ` Rusty Russell
2002-11-11 12:03 ` Horst von Brand
2002-11-11 12:35 ` Richard B. Johnson
2002-11-05 0:47 ` [PATCH] Module loader against 2.5.46: 9/9 Rusty Russell
2002-11-06 12:43 ` Keith Owens
2002-11-07 11:08 ` Rusty Russell
2002-11-08 9:35 ` Russell King
2002-11-09 3:01 ` Rusty Russell [this message]
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=20021109041543.D3F902C283@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
Powered by JetHome