Hi Eric, > 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.
Hmm, restricting System RAM only may be too pessimistic. (One of motivations of this work is for using /dev/mem safely. "dd if=/dev/mem of=xxx" causes panic on my amd64(8GB mem) machine since reading from address around 0xfe000000 causes a machine check. hmm, this area is marked as "reserved". not ACPI area. ACPI area can be read.) Ok, I will add a type field. > The other direction something like this can go is to dump > the data structures in linux/mmzone.h Do you mean defining a data structure in linux/mmzone.h ? I used to think a particular struct is not necessary for this work, but now I think it is better to define a struct for this. Let me consider. > 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. I am looking forward this :-) And, you mentioned a couple of weeks ago: > Anyway one thing I want to do is actually drop the apic shutdown > code altogether in this code path. I threw it in there to > ease the transition from the old code base to the new, but > if that code is causing issues.... So this is probably a good time > to start testing that. How about this ? Thanks. -- Itsuro ODA <[EMAIL PROTECTED]> - 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/
