From: Huang Ying <ying.huang@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Pavel Ivanov <paivanof@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>
Subject: Re: APEI: Can not request iomem region for GARs
Date: Tue, 30 Aug 2011 08:57:14 +0800 [thread overview]
Message-ID: <4E5C356A.7000701@intel.com> (raw)
In-Reply-To: <CAErSpo7=SZ1XKBY0dDUg-c+_d-GoZF7uNypQc3Ecm+iofkXTMA@mail.gmail.com>
On 08/29/2011 10:48 PM, Bjorn Helgaas wrote:
> On Sun, Aug 28, 2011 at 7:27 PM, Huang Ying <ying.huang@intel.com> wrote:
>> On 08/26/2011 09:43 PM, Bjorn Helgaas wrote:
>>> On Thu, Aug 25, 2011 at 10:13 PM, Huang Ying <ying.huang@intel.com> wrote:
>>>> Hi, Pavel,
>>>>
>>>> Sorry, there is a minor issue in the patch. Do you have time to try
>>>> the updated version attached.
>>>
>>> I think Yinghai's patch is a better approach (though it needs a changelog).
>>>
>>> The ACPI NVS space should not be marked as "busy" by the e820 code in
>>> the iomem_resource tree.
>>>
>>> It's way too complicated to mess around with registering NVS space and
>>> trying to deal with it specially in APEI.
>>
>> ACPI NVS is different, it can be used only by firmware, and its
>> interpreter, such as ACPI AML interpreter and APEI interpreter. It can
>> not be used by ordinary driver. If my understanding is correct, this is
>> why ACPI NVS is marked as busy.
>
> I don't understand why ACPI NVS is different. If we reserve it in
> iomem_resource (without marking it busy), it's already unavailable to
> anything else unless you know something connected to the NVS region.
I think ACPI NVS can be seen as reserved by ACPI or firmware
interpreter. So that, all other drivers should not access it.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2011-08-30 0:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 3:43 APEI: Can not request iomem region for GARs Pavel Ivanov
2011-08-19 21:48 ` Bjorn Helgaas
2011-08-22 5:43 ` Huang Ying
2011-08-22 7:12 ` Huang Ying
2011-08-22 16:45 ` Bjorn Helgaas
2011-08-22 21:04 ` Yinghai Lu
2011-08-23 0:32 ` Huang Ying
2011-08-25 2:45 ` Pavel Ivanov
2011-08-26 4:13 ` Huang Ying
2011-08-26 13:43 ` Bjorn Helgaas
2011-08-29 1:27 ` Huang Ying
2011-08-29 14:48 ` Bjorn Helgaas
2011-08-30 0:57 ` Huang Ying [this message]
2011-08-27 3:28 ` Pavel Ivanov
2011-08-29 1:15 ` Huang Ying
2011-08-29 4:10 ` Pavel Ivanov
2011-08-29 5:22 ` Huang Ying
2011-08-29 14:43 ` Pavel Ivanov
2011-08-30 0:55 ` Huang Ying
2011-08-29 5:37 ` Huang Ying
2011-09-03 2:44 ` Pavel Ivanov
2011-09-05 2:05 ` 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=4E5C356A.7000701@intel.com \
--to=ying.huang@intel.com \
--cc=bhelgaas@google.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paivanof@gmail.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