From: Gary Hade <garyhade@us.ibm.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Xiao, Hui" <hui.xiao@linux.intel.com>,
garyhade@us.ibm.com, tony.luck@intel.com, ying.huang@intel.com,
lenb@kernel.org, pluto@agmk.net, linux-acpi@vger.kernel.org,
Chen Gong <gong.chen@linux.intel.com>
Subject: Re: [RFC] ACPI, APEI: Fix incorrect bit width + offset check condition
Date: Thu, 14 Jun 2012 14:49:06 -0700 [thread overview]
Message-ID: <20120614214906.GA11309@us.ibm.com> (raw)
In-Reply-To: <20120614095330.7d797f1d@endymion.delvare>
On Thu, Jun 14, 2012 at 09:53:30AM +0200, Jean Delvare wrote:
> Hi Hui,
>
> On Wed, 13 Jun 2012 18:44:15 +0800, Xiao, Hui wrote:
< snip >
>
> > Besides if addressing a data structure, per ACPI spec bit_width and bit_offset
> > must be zero, the original condition will always end with error even valid
> > access width is given.
>
> I agree that the original test did not support the data structure case.
> OTOH after quickly reading the relevant page of the ACPI specification,
> I do not understand how the structure size is passed, so I have no idea
> how this case could be handled.
I wasn't able to find any references to the Generic Address
Structure (GAS) in the APEI portion of the ACPI spec implying
data structure access via an address contained in a GAS. However,
I believe it is a good idea to cover the data structure case in the
event that the code is ever used beyond APEI where the data structure
case could become an issue.
Hui, Please check my assertion that the data structure case is
not a factor for APEI.
Thanks,
Gary
--
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503 IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc
next prev parent reply other threads:[~2012-06-14 21:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 7:39 [RFC] ACPI, APEI: Fix incorrect bit width + offset check condition Xiao, Hui
2012-06-13 8:46 ` Jean Delvare
2012-06-13 10:44 ` Xiao, Hui
2012-06-14 7:53 ` Jean Delvare
2012-06-14 21:49 ` Gary Hade [this message]
2012-06-13 17:45 ` Gary Hade
2012-06-14 6:14 ` Xiao, Hui
2012-06-14 8:09 ` Jean Delvare
2012-06-14 16:32 ` Gary Hade
2012-06-15 11:28 ` Xiao, Hui
2012-07-18 8:24 ` Chen Gong
2012-07-18 14:28 ` Jean Delvare
2012-07-19 0:37 ` 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=20120614214906.GA11309@us.ibm.com \
--to=garyhade@us.ibm.com \
--cc=gong.chen@linux.intel.com \
--cc=hui.xiao@linux.intel.com \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=pluto@agmk.net \
--cc=tony.luck@intel.com \
--cc=ying.huang@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).