From: "H. Peter Anvin" <hpa@zytor.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: Borislav Petkov <bp@amd64.org>, Greg KH <greg@kroah.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
"mikew@google.com" <mikew@google.com>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
"tj@kernel.org" <tj@kernel.org>,
"fweisbec@gmail.com" <fweisbec@gmail.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [RFC][PATCH] pstore: EFI Support
Date: Tue, 10 May 2011 13:44:18 -0700 [thread overview]
Message-ID: <4DC9A3A2.20000@zytor.com> (raw)
In-Reply-To: <5C4C569E8A4B9B42A84A977CF070A35B2C16FB4815@USINDEVS01.corp.hds.com>
On 05/10/2011 12:18 PM, Seiji Aguchi wrote:
> Hi,
>
> Thank you for your comments.
>
>> Btw, is this case of the possibility for APEI of corrupting NVRAM
>> storage something you actually experienced on a real machine or simply a
>> conclusion from looking at APEI code doing ioremap()?
>
> I simply concluded from looking at ioremap() of APEI code.
>
The thing is that you're effectively betting that the EFI method will be
less broken than our kernels. That is not at all given...
-hpa
next prev parent reply other threads:[~2011-05-10 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 15:00 [RFC][PATCH] pstore: EFI Support Seiji Aguchi
2011-05-10 16:11 ` Greg KH
2011-05-10 16:57 ` Borislav Petkov
2011-05-10 19:18 ` Seiji Aguchi
2011-05-10 20:44 ` H. Peter Anvin [this message]
2011-05-11 13:09 ` Américo Wang
2011-05-11 14:27 ` H. Peter Anvin
2011-05-12 1:46 ` Matthew Garrett
2011-05-10 20:52 ` Luck, Tony
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=4DC9A3A2.20000@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@amd64.org \
--cc=dle-develop@lists.sourceforge.net \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.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.