abatron and kernel modules.

David Updegraff dave at cray.com
Fri Jul 26 03:13:37 EST 2002


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?


Dave Updegraff, Cray Inc. / dave at cray.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

More information about the Linuxppc-embedded mailing list