From: Greg KH <greg@kroah.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
tglx@linutronix.de, mingo@elte.hu, akpm@linux-foundation.org,
ying.huang@intel.com, Borislav Petkov <bp@alien8.de>,
David Miller <davem@davemloft.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jim Keniston <jkenisto@linux.vnet.ibm.com>,
Kyungmin Park <kmpark@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [RFC] persistent store (version 2) (part 1 of 2)
Date: Tue, 30 Nov 2010 16:58:51 -0800 [thread overview]
Message-ID: <20101201005851.GA31571@kroah.com> (raw)
In-Reply-To: <4cf594e21679631af0@agluck-desktop.sc.intel.com>
On Tue, Nov 30, 2010 at 04:20:50PM -0800, Luck, Tony wrote:
> Here's version 2 with most of the fixes suggested in the discussion
> for version 1 (see http://marc.info/?l=linux-arch&m=129045078803118&w=2).
>
> Stuff that I haven't done:
>
> 1) Still has the "daft" echo filename > erase to clear entries from the
> persistent store. I looked hard at /sys and can't see how to get a
> notification for an unlink(2). If I'm missing something, would somebody
> please send me a clue. If this is a fatal flaw - then this will have to
> move to debugfs (or turn into its own filesystem type). But I'd really
> prefer to not give up the convenience of /sys
>
> 2) Did not implement Jim's suggestion to save OOPs ... I'm not at
> all sure how to let the user configure this. mtdoops.c has a module
> parameter for it - but I gave up on letting pstore be a module ...
> it needs to be initialized before the platform driver, and there doesn't
> seem to be much point in having it be unloadable.
>
> I did write the ERST platform hooks (they are part 2 of 2, but I'd advise
> the faint of heart not to look too closely at the ACPI/APEI'isms involved).
> Here's a sample of what it looks like (with a debug call to panic() from
> the pstore_erase() function added for testing purposes):
>
> $ cd /sys/firmware/pstore
As you are adding new sysfs files, you are required to document them in
Documentation/ABI/ as well.
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-01 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 0:20 [RFC] persistent store (version 2) (part 1 of 2) Luck, Tony
2010-12-01 0:58 ` Greg KH [this message]
2010-12-01 18:01 ` Luck, Tony
2010-12-01 22:10 ` Greg KH
2010-12-02 0:51 ` Andrew Morton
2010-12-02 6:00 ` Luck, Tony
2010-12-02 10:12 ` Andrew Morton
2010-12-02 16:19 ` Tony Luck
2010-12-02 18:45 ` Tony Luck
2010-12-02 18:45 ` Tony Luck
2010-12-02 8:26 ` Huang Ying
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=20101201005851.GA31571@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jkenisto@linux.vnet.ibm.com \
--cc=kmpark@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).