From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Matt Fleming <matt@console-pimps.org>,
linux-efi <linux-efi@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile devices")
Date: Thu, 10 Apr 2014 20:57:24 +0200 [thread overview]
Message-ID: <20140410185724.GC4704@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31E2465C@ORSMSX106.amr.corp.intel.com>
On Thu, Apr 10, 2014 at 06:34:34PM +0000, Luck, Tony wrote:
> Speed is also a factor ... waiting for flash to update for each
> printk() would mess up timing so much that you might not see the
> problem you are chasing.
Gaah, there's that too. I guess nvram access speeds slower than in the
msec range (I'm looking at my printk timestamps) are no good for us.
> A better EFI trick for this would be "capsules". They live in regular
> RAM and BIOS firmware does stuff with them at warm reset time. Matt
> has been looking at them - but BIOS support for them seems sketchy to
> none right now.
Hmm, I'm wondering whether we could put a bunch of sanity checks into
fwts to run on a box and check needed capsules functionality before
logging to one.
Matt, looks like we have ourselves a new project. :-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2014-04-10 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 18:15 df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile devices") Borislav Petkov
2014-04-10 18:15 ` Borislav Petkov
2014-04-10 18:34 ` Luck, Tony
2014-04-10 18:34 ` Luck, Tony
2014-04-10 18:57 ` Borislav Petkov [this message]
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=20140410185724.GC4704@pd.tnic \
--to=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.