linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Huang\, Ying" <ying.huang@intel.com>
To: Borislav Petkov <bp@suse.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Huang, Ying" <ying.huang@intel.com>, Len Brown <lenb@kernel.org>,
	Tomasz Nowicki <tomasz.nowicki@linaro.org>,
	Tony Luck <tony.luck@intel.com>, Fu Wei <fu.wei@linaro.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI, APEI: Fix BERT resources conflict with ACPI NVS area
Date: Thu, 16 Feb 2017 18:24:39 +0800	[thread overview]
Message-ID: <87fujea0wo.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20170216095230.ecbb6hfqmcpk3jbw@pd.tnic> (Borislav Petkov's message of "Thu, 16 Feb 2017 10:52:30 +0100")

Borislav Petkov <bp@suse.de> writes:

> On Thu, Feb 16, 2017 at 12:42:00AM +0100, Rafael J. Wysocki wrote:
>> On Tuesday, February 14, 2017 10:01:13 AM Huang, Ying wrote:
>> > From: Huang Ying <ying.huang@intel.com>
>> > 
>> > It was reported that some firmware will use ACPI NVS area for BERT
>> > address range.  This will cause resources conflict because the ACPI
>> > NVS area is marked as busy already.  Fix this via excluding ACPI NVS
>> > area when requesting IO resources for BERT.
>> > 
>> > Reported-and-tested-by: Hans Kristian Rosbach <hansr@raskesider.no>
>> > Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
>> 
>> Boris, what do you think?
>
> Lemme see, so the BERT is for hw errors which have happened during the
> previous boot and the machine couldn't handle them. So they do get saved
> in some mem in the fw for inspection during the next boot.
>
> And "some firmware" has decided to write them into non-volatile storage
> - because you should never ever forget those errors! :-)
>
> And I don't understand the "fix" here: we're excluding the NVS area when
> mapping the BERT table but then how are we supposed to read those errors
> from there?

The NVS area is excluded when request the resources, because the NVS
area has been marked as busy already.  But the whole BERT memory area is
mapped, so we can read from it.

> Or am I missing something obvious?

Best Regards,
Huang, Ying

  reply	other threads:[~2017-02-16 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14  2:01 [PATCH] ACPI, APEI: Fix BERT resources conflict with ACPI NVS area Huang, Ying
2017-02-14 18:44 ` Baicar, Tyler
2017-02-15 23:42 ` Rafael J. Wysocki
2017-02-16  9:52   ` Borislav Petkov
2017-02-16 10:24     ` Huang, Ying [this message]
2017-02-16 10:32       ` Borislav Petkov
2017-02-17  0:31         ` Huang, Ying
2017-02-17 10:02           ` Borislav Petkov
2017-02-20  0:56             ` 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=87fujea0wo.fsf@yhuang-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=bp@suse.de \
    --cc=fu.wei@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tomasz.nowicki@linaro.org \
    --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).