All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Asbock <masbock@linux.vnet.ibm.com>
To: gong.chen@intel.com, linux-acpi@vger.kernel.org,
	ying.huang@intel.com, naveen.n.rao@in.ibm.com
Subject: Re: APEI: ERST table in ACPI NVS not supported
Date: Mon, 04 Feb 2013 09:06:24 -0800	[thread overview]
Message-ID: <510FEA90.8060503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130204092018.GA22035@gchen.bj.intel.com>

On 02/04/2013 01:20 AM, Chen Gong wrote:
> On Tue, Jan 29, 2013 at 10:08:11AM -0800, Max Asbock wrote:
>
>
> we have systems that declare the memory range for ERST in ACPI NVS.
> Because ACPI NVS is marked 'busy' by e820_reserve_resources() the
> call to request_mem_region(erst_erange.base, erst_erange.size, "APEI
> ERST") made from erst_init() fails and we get:
> ERST: Can not request iomem region<0x        7e91f000-0x
> 7e920c00>  for ERST.
>
> I did notice that quite some effort was made to add code to avoid
> resource conflicts between APEI and ACPI NVS. But ERST still goes
> straight to request_mem_region() which is bound to fail. I am
> assuming this should go through apei_resources_request() instead or
> I am missing something?
>
> If my understanding is right, after ERST resource is requested via
> apei_resources_request and when requesting error log address range,
> you meet an NVS conflict, right?
>
> If so, NVS must be excluded. But I'm afraid if error range is
> separated into two parts thus some errors will be lost. Would you
> please paste errage address range and conflicted NVS range?
ACPI NVS is:

[    0.000000] BIOS-e820: [mem 0x000000007e6a5000-0x000000007ebc5fff] 
ACPI NVS

ERST erange is:

0x7e91f000-0x7e920c00

which is a single range entirely within ACPI NVS.

thanks,
Max




  reply	other threads:[~2013-02-04 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 18:08 APEI: ERST table in ACPI NVS not supported Max Asbock
2013-02-04  9:20 ` Chen Gong
2013-02-04 17:06   ` Max Asbock [this message]
2013-02-05  1:56     ` Chen Gong

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=510FEA90.8060503@linux.vnet.ibm.com \
    --to=masbock@linux.vnet.ibm.com \
    --cc=gong.chen@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=naveen.n.rao@in.ibm.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 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.