RE: Figuring out physical memory regions from a kernel module

[Dave Hansen]

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:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm4/broken-out/

-- 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  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/