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, 21 Nov 2011 08:43:47 +0800 [thread overview]
Message-ID: <1321836227.13860.121.camel@yhuang-dev> (raw)
In-Reply-To: <5C4C569E8A4B9B42A84A977CF070A35B2C57B4FA66@USINDEVS01.corp.hds.com>
On Sat, 2011-11-19 at 07:04 +0800, Seiji Aguchi wrote:
> Hi,
>
> >According to ACPI 4.0a spec:
> >
> >"""
> >17.5.2.4.1 Error Log Address Range Resides in NVRAM
> >
>
> Thank you for giving me the information.
> Let me clarify one thing.
>
> If the busy bit can be cleared immediately, we don't need to
> check busy bit with CHECK_BUSY_STATUS.
> So, we should simply execute OSPM operations as follows.
>
> - Writing
> 1. BEGIN_WRITE
> 2. SET_RECORD_OFFSET
> 3. EXECUTE_OPERATION
> 4. END
>
> - Reading
> 1. BEGIN_READ
> 2. SET_RECORD_OFFSET
> 3. SET_RECORD_ID
> 4. EXECUTE_OPERATION
> (END operation is not needed because OSPM requires no platform
> support to read.)
>
> - Clearing
> 1. BEGIN_CLEAR
> 2. SET_RECORD_ID
> 3. EXECUTE_OPERATION
> (END operation is not needed because OSPM requires no platform
> support to clear.)
>
> Is this what you expected?
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.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2011-11-21 0:43 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 [this message]
2011-12-15 16:03 ` Seiji Aguchi
2011-12-19 1:24 ` Huang Ying
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=1321836227.13860.121.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).