RE: Figuring out physical memory regions from a kernel module

From: Dave Hansen
Date: Wed Dec 08 2004 - 13:42:22 EST

On Wed, 2004-12-08 at 10:28, Hanson, Jonathan M wrote:
> The module is dumping the contents of physical memory
> and saving the architecture state of the system to a file when triggered
> (ioctl call). What I have works but I need to extend it to systems other
> than my own where I have hard-coded the system RAM regions into the
> code. I need the physical addresses of memory because the tool I feed
> this output into requires this. Here is an example of what the memory
> file looks like:

Sounds like crash dumping. I think they've already run into and
addressed the same general problems.

See crashdump-*.patch in here:

-- Dave

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at