Date: Sun, 21 Nov 2010 13:14:53 -0800 (PST)
Message-Id: <20101121.131453.48488717.davem@davemloft.net>
To: tony.luck@intel.com
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
        tglx@linutronix.de, mingo@elte.hu, greg@kroah.com,
        akpm@linux-foundation.org, ying.huang@intel.com
Subject: Re: [RFC] persistent store
From: David Miller <davem@davemloft.net>
In-Reply-To: <4ce85e437577ae827@agluck-desktop.sc.intel.com>
References: <4ce85e437577ae827@agluck-desktop.sc.intel.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1226
Lines: 27

From: "Luck, Tony" <tony.luck@intel.com>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/