Itsuro Oda <[EMAIL PROTECTED]> writes: > Hi, Eric and all > > Attached is an implementation of /proc/cpumem. > /proc/cpumem shows the valid physical memory ranges.
Interesting. My imagination when I proposed this was something based on struct resource that works like /proc/iomem on x86 but can be meaningfully be used on systems with where ram lives in a separate address space from io device memory. > example: amd64 8GB Mem > # cat /proc/cpumem > 0000000000000000 000000000009b800 > 0000000000100000 00000000fbe70000 > 0000000100000000 0000000100000000 > # > start address and size. hex digit. The lack of a type field looses a fair amount of functionality compared to /proc/iomem. In particular you can't see where the ACPI data is. The other direction something like this can go is to dump the data structures in linux/mmzone.h > Any comments, recomendations and suggestions are welcom. > > BTW, does not kexec/kdump run on 2.6.11-rc3-mm2 ? > How do I get and examine the latest kexec/kdump ? I'm not quite certain what is happening. I have been playing with kexec user space a little bit and a new development release is at: http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz I have written a first pass at a user space core dump generator, using /dev/mem. /sbin/kexec still needs some work to prepare the ELF headers before a crash. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
