mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	Tomasz Nowicki <tomasz.nowicki@linaro.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -v2] ACPI, APEI: Fix BERT resources conflict with ACPI NVS area
Date: Mon, 20 Feb 2017 10:44:19 +0100	[thread overview]
Message-ID: <20170220094419.j6effubsn7qct55q@pd.tnic> (raw)
In-Reply-To: <20170220011343.6736-1-ying.huang@intel.com>

On Mon, Feb 20, 2017 at 09:12:58AM +0800, Huang, Ying wrote:
> From: Huang Ying <ying.huang@intel.com>
> 
> It was reported that on some machines, there is overlap between ACPI
> NVS area and BERT address range.  This appears reasonable because BERT
> contents need to be non-volatile across reboot.  But this will cause
> resources conflict in current Linux kernel implementation because the
> ACPI NVS area is marked as busy.  The resource conflict is fixed via
> excluding the ACPI NVS area when requesting IO resources for BERT.
> When accessing the BERT contents, the whole BERT address range will be
> ioremapped and accessed.
> 
> Reported-and-tested-by: Hans Kristian Rosbach <hansr@raskesider.no>
> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
> ---
>  drivers/acpi/apei/bert.c | 20 ++++++++++++--------
>  1 file changed, 12 insertions(+), 8 deletions(-)

Acked-by: Borislav Petkov <bp@suse.de>

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

      reply	other threads:[~2017-02-20  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20  1:12 Huang, Ying
2017-02-20  9:44 ` Borislav Petkov [this message]

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=20170220094419.j6effubsn7qct55q@pd.tnic \
    --to=bp@suse.de \
    --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=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

all inboxes | Powered by JetHome®