RE: [2.6.6 PATCH] Exposing EFI memory map

[Dave Hansen]

On Wed, 2004-05-12 at 03:24, Sourav Sen wrote:
> Maybe. But the point I had in mind is, say for example
> memory diagnostics applications/exercisers which reads (Blind
> reads, without caring about contents) memory
> to uncover errors (single bit errors) can use
> this to know the usable ranges and map them thru /dev/mem and
> read those ranges.

If you expose the EFI memory map, then you'll be able to write memory
diagnostics that will work on any EFI-based machine.

If you expose the EFI memory map in an architecture-independent fashion,
then you'll be able to write diagnostics that will work on any *Linux*
machine, plus all of the EFI machines.  Plus, by doing it first, you get
to greatly influence how the arch-independent stuff is done to make your
life the easiest.  

Think /sys/system/devices/memory, not /sys/firmware/efi.

We're planning on doing this anyway for memory hotplug, so some of the
work and ideas are already there.  I'd be happy to point you to some
past discussions and code on the subject.  

-- 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/