[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1324257869.4639.1.camel@yhuang-dev>
Date: Mon, 19 Dec 2011 09:24:29 +0800
From: Huang Ying <ying.huang@...el.com>
To: Seiji Aguchi <seiji.aguchi@....com>
Cc: "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lenb@...nel.org" <lenb@...nel.org>,
"Luck, Tony" <tony.luck@...el.com>,
"Chen, Gong" <gong.chen@...el.com>,
Matthew Garrett <mjg@...hat.com>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Satoru Moriya <satoru.moriya@....com>
Subject: RE: [RFC][PATCH]ACPI,APEI,ERST, back end driver for NVRAM
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists