From: "Luck, Tony"
Date: Sat, 20 Nov 2010 15:48:19 -0800
> The usage model I'm envisioning is that a platform driver
> will register with this code to provide the actual storage.
> I've tried to make this interface general, but I'm working
> from a sample of one (the ACPI ERST code), so if anyone else
> has some persistent store that can't be handled by this code,
> speak up and we can put in the necessary tweaks.
> My assumptions are that the data that Linux cares about will
> be wrapped in some error record structure with a header, and
> possibly a footer that the device code needs. So the driver
> specifies how much padding to put around a buffer to make
> life easy for it. It also specifies the maximum number of
> bytes that can be saved in one record.
Thanks for doing this work Tony.
On sparc64 I can mark an arbitrary region of physical memory
as persistent across soft reboots. So I'll likely use that
to implement these interfaces.