From: David Updegraff <dave@cray.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: abatron and kernel modules.
Date: Thu, 25 Jul 2002 12:13:37 -0500 (CDT) [thread overview]
Message-ID: <200207251713.MAA00232@mint.mw.cray.com> (raw)
Hi.
We've been very happily using BDI2000 for kernel debugging on our 405GP
on a 2.4.2 kernel with builtin abatron MMU support (via PTBASE at 0xf0).
But I have not figured out how to get it deal with the address space of
a loaded kernel module: it claims that the region is missing from the
page tables. Kernel addresses are in 0xC00xxxxx ranges, and when we load
the module, 'module_list' now points to 0xC340xxxx ranges. BDI can
dump the physical addresses of my module, but cant talk to the virual
kernel address space of the loaded module.
Is there some page table magic that goes on with module loading that
is confusing both me and the BDI?
Thanx.
--
Dave Updegraff, Cray Inc. / dave@cray.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-25 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 17:13 David Updegraff [this message]
2002-07-25 19:45 ` abatron and kernel modules Dan Malek
2002-07-25 20:11 ` John W. Linville
2002-07-25 20:54 ` Dan Malek
2002-07-25 19:53 ` Wolfgang Denk
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=200207251713.MAA00232@mint.mw.cray.com \
--to=dave@cray.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).