From: valdis.kletnieks@vt.edu
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Luck, Tony (tony.luck@intel.com)" <tony.luck@intel.com>,
"mikew@google.com" <mikew@google.com>,
"dzickus@redhat.com" <dzickus@redhat.com>,
"Matthew Garrett (mjg@redhat.com)" <mjg@redhat.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [RFC][PATCH v2 0/3] efi_pstore: avoid losing critical message
Date: Sat, 21 Jul 2012 16:52:22 -0400 [thread overview]
Message-ID: <54552.1342903942@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 19 Jul 2012 21:11:44 -0000." <A5ED84D3BB3A384992CBB9C77DEDA4D40FB27FAA@USINDEM103.corp.hds.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Thu, 19 Jul 2012 21:11:44 -0000, Seiji Aguchi said:
> [Solution]
> To avoid losing a critical message, this patchset is based on a following concept.
> - A basic policy is _not_ to overwrite existing entries.
>
> - However, if kernel panics while a system is rebooting, a critical message
> can't be saved by the policy above.
> (In this case, panic message is critical.)
OK, system boots in "overwrite mode", and when done booting, we go into
"non-overwrite mode". Makes sense to me. Only part I'm missing is how/when/why
we leave overwrite mode - what makes the change, and how?
(If I missed an ioctl or /sys entry or something that userspace toggles to say "I'll
take care of it from here", please point me at it and I'll go re-read after I find
some more caffeine ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-07-21 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 21:11 [RFC][PATCH v2 0/3] efi_pstore: avoid losing critical message Seiji Aguchi
2012-07-21 20:52 ` valdis.kletnieks [this message]
2012-07-23 14:13 ` Matthew Garrett
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=54552.1342903942@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=dle-develop@lists.sourceforge.net \
--cc=dzickus@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=mjg@redhat.com \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=tony.luck@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).