All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Gary Hade <garyhade@us.ibm.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Lans Zhang <jia.zhang@windriver.com>,
	len.brown@intel.com, linux-acpi@vger.kernel.org,
	Myron Stowe <mstowe@redhat.com>,
	Huang Ying <ying.huang@intel.com>
Subject: Re: [PATCH] ACPI, APEI: Fixup incorrect 64-bit access width firmware bug
Date: Fri, 18 Jan 2013 09:50:19 +0100	[thread overview]
Message-ID: <1358499019.4763.49.camel@amber.site> (raw)
In-Reply-To: <20130117222754.GA32229@us.ibm.com>

Le jeudi 17 janvier 2013 à 14:27 -0800, Gary Hade a écrit :
> On Wed, Jan 16, 2013 at 11:54:54PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, January 16, 2013 05:03:29 PM Lans Zhang wrote:
> > > The bit width check was introduced by 15afae60 (ACPI, APEI: Fix
> > > incorrect APEI register bit width check and usage), and a fixup
> > > for incorrect 32-bit width memory address was given by f712c71
> > > (ACPI, APEI: Fixup common access width firmware bug). Now there
> > > is a similar symptom:
> > > 
> > > [Firmware Bug]: APEI: Invalid bit width + offset in GAR [0x12345000/64/0/3/0]
> > > 
> > > Another bogus BIOS reports an incorrect 64-bit width in trigger table.
> > > Thus, apply to a similar workaround for 64-bit width memory address.
> > 
> > This makes sense to me, but I'd like more people to have a look at it (Myron,
> > Ying, Gary CCed).
> > 
> > Thanks,
> > Rafael
> > 
> > 
> > > Signed-off-by: Lans Zhang <jia.zhang@windriver.com>
> > > ---
> > >  drivers/acpi/apei/apei-base.c |    3 +++
> > >  1 files changed, 3 insertions(+), 0 deletions(-)
> > > 
> > > diff --git a/drivers/acpi/apei/apei-base.c b/drivers/acpi/apei/apei-base.c
> > > index 00a7836..46f80e2 100644
> > > --- a/drivers/acpi/apei/apei-base.c
> > > +++ b/drivers/acpi/apei/apei-base.c
> > > @@ -590,6 +590,9 @@ static int apei_check_gar(struct acpi_generic_address *reg, u64 *paddr,
> > >  	if (bit_width == 32 && bit_offset == 0 && (*paddr & 0x03) == 0 &&
> > >  	    *access_bit_width < 32)
> > >  		*access_bit_width = 32;
> > > +	else if (bit_width == 64 && bit_offset == 0 && (*paddr & 0x07) == 0 &&
> > > +	    *access_bit_width < 64)
> > > +		*access_bit_width = 64;
> > >  
> > >  	if ((bit_width + bit_offset) > *access_bit_width) {
> > >  		pr_warning(FW_BUG APEI_PFX
> > > 
> > -- 
> > I speak only for myself.
> > Rafael J. Wysocki, Intel Open Source Technology Center.
> > 
> 
> This looks reasonable to me.
> Acked-by: Gary Hade <garyhade@us.ibm.com>
> 
> Copying Jean Delvare who authored the 32-bit fixup.

I've not seen this specific case yet but yes, the fixup seems perfectly
reasonable.

Acked-by: Jean Delvare <jdelvare@suse.de>


-- 
Jean Delvare
Suse L3

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-01-18  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16  9:03 [PATCH] ACPI, APEI: Fixup incorrect 64-bit access width firmware bug Lans Zhang
2013-01-16 22:54 ` Rafael J. Wysocki
2013-01-17 22:27   ` Gary Hade
2013-01-18  8:50     ` Jean Delvare [this message]
2013-01-18  2:50   ` Myron Stowe

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=1358499019.4763.49.camel@amber.site \
    --to=jdelvare@suse.de \
    --cc=garyhade@us.ibm.com \
    --cc=jia.zhang@windriver.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mstowe@redhat.com \
    --cc=rjw@sisk.pl \
    --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 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.