All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, John Levon <levon@movementarian.org>
Subject: Re: New module loader makes kernel debugging much harder
Date: Mon, 25 Nov 2002 12:26:58 +1100	[thread overview]
Message-ID: <20021125122658.0bb41aed.rusty@rustcorp.com.au> (raw)
In-Reply-To: <25797.1038100726@ocs3.intra.ocs.com.au>

On Sun, 24 Nov 2002 12:18:46 +1100
Keith Owens <kaos@ocs.com.au> wrote:
> One possibility the new loader opens up is the ability to replicate the
> pure module data (rodata and text) for each node of a NUMA box.  There
> is already an option to replicate the kernel text on each node to cut
> down inter-node traffic.  Replicating the pure module data would be
> nice as well.  I guarantee that will result in something that is not
> "simply mapped".

Ewww, you are a sick lad 8)

But I'm not sure that there is any interface which wouldn't break horribly
when faced with that possibility.

The patch to restore /proc/ksyms is trivial.  As is the addition of a start
entry /proc/modules.  When combined with rth's simplified loader, it should
be sufficient for both ksymoops and oprofile.

kgdb needs a patch to work, anyway: you might want to restore /proc/ksyms
in that patch?  (I don't use kgdb, so my ignorance here is complete).

Rusty.
-- 
   there are those who do and those who hang on and you don't see too
   many doers quoting their contemporaries.  -- Larry McVoy

  parent reply	other threads:[~2002-11-25  1:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  2:20 New module loader makes kernel debugging much harder Keith Owens
2002-11-23  2:35 ` John Levon
2002-11-23  2:43   ` Keith Owens
2002-11-23 16:23     ` John Levon
2002-11-24  0:49       ` Keith Owens
2002-11-24  1:06         ` John Levon
2002-11-24  1:18           ` Keith Owens
2002-11-24  1:34             ` John Levon
2002-11-25  1:26             ` Rusty Russell [this message]
2002-11-23  4:22 ` Jamie Lokier

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=20021125122658.0bb41aed.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=kaos@ocs.com.au \
    --cc=levon@movementarian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.