From: David Miller <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
Date: Sun, 21 Nov 2010 13:14:53 -0800 (PST) [thread overview]
Message-ID: <20101121.131453.48488717.davem@davemloft.net> (raw)
In-Reply-To: <4ce85e437577ae827@agluck-desktop.sc.intel.com>
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.
next prev parent reply other threads:[~2010-11-21 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 23:48 [RFC] persistent store Luck, Tony
2010-11-21 9:07 ` Borislav Petkov
2010-11-21 21:47 ` Tony Luck
2010-11-21 21:47 ` Tony Luck
2010-11-22 7:32 ` Borislav Petkov
2010-11-22 7:48 ` Borislav Petkov
2010-11-21 21:14 ` David Miller [this message]
2010-11-22 1:59 ` Huang Ying
2010-11-22 10:43 ` Alan Cox
2010-11-22 18:17 ` Tony Luck
2010-11-22 16:55 ` Tony Luck
2010-11-22 16:55 ` Tony Luck
2010-11-22 18:24 ` Geert Uytterhoeven
2010-11-22 18:33 ` Tony Luck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101121.131453.48488717.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox