From: "Baicar, Tyler" <tbaicar@codeaurora.org>
To: "Huang, Ying" <ying.huang@intel.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>,
Tomasz Nowicki <tomasz.nowicki@linaro.org>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@suse.de>,
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: Tue, 14 Feb 2017 11:44:56 -0700 [thread overview]
Message-ID: <1e80dbf3-c7d3-2bba-1032-ce775a2ea8a5@codeaurora.org> (raw)
In-Reply-To: <20170214020143.29713-1-ying.huang@intel.com>
On 2/13/2017 7:01 PM, 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>
Tested-by: Tyler Baicar <tbaicar@codeaurora.org>
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-02-14 18:45 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 [this message]
2017-02-15 23:42 ` Rafael J. Wysocki
2017-02-16 9:52 ` Borislav Petkov
2017-02-16 10:24 ` Huang, Ying
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=1e80dbf3-c7d3-2bba-1032-ce775a2ea8a5@codeaurora.org \
--to=tbaicar@codeaurora.org \
--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 \
--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