From: Huang Ying <ying.huang@intel.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"Chen, Gong" <gong.chen@intel.com>,
Matthew Garrett <mjg@redhat.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: RE: [RFC][PATCH]ACPI,APEI,ERST, back end driver for NVRAM
Date: Mon, 19 Dec 2011 09:24:29 +0800 [thread overview]
Message-ID: <1324257869.4639.1.camel@yhuang-dev> (raw)
In-Reply-To: <5C4C569E8A4B9B42A84A977CF070A35B2C57F7ADB5@USINDEVS01.corp.hds.com>
On Fri, 2011-12-16 at 00:03 +0800, Seiji Aguchi wrote:
> Hi,
>
> >
> >No. I have different understanding.
> >
> >Because error log address range resides in NVRAM, the contents will be
> >reserved even after reboot. So we do not need read/clear operations at
> >all, and should place all records in error log address range.
>
> I have a quick question about your comment above.
> Do you know whether this optimization of read/clear operations works
> on machines which APEI is enabled by WHEA _OSC call?
I have no machine with
!!(erst_erange.attr & ERST_RANGE_NVRAM) == 1
Do you have?
Best Regards,
Huang Ying
prev parent reply other threads:[~2011-12-19 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 20:47 [RFC][PATCH]ACPI,APEI,ERST, back end driver for NVRAM Seiji Aguchi
2011-11-18 1:59 ` Huang Ying
2011-11-18 23:04 ` Seiji Aguchi
2011-11-21 0:43 ` Huang Ying
2011-12-15 16:03 ` Seiji Aguchi
2011-12-19 1:24 ` Huang Ying [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=1324257869.4639.1.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=gong.chen@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).