linux-kernel - Re: APEI: Can not request iomem region for GARs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Aug 2011 08:32:16 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Pavel Ivanov <paivanof@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"lenb@...nel.org" <lenb@...nel.org>
Subject: Re: APEI: Can not request iomem region for GARs

On 08/23/2011 05:04 AM, Yinghai Lu wrote:
> On Mon, Aug 22, 2011 at 9:45 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>> On Mon, Aug 22, 2011 at 1:12 AM, Huang Ying <ying.huang@...el.com> wrote:
>>> Do you have time to try the patch attached with the mail?
>>> acpi_nvs.patch should go first.
>>
>> In this case, we have an ACPI NVS region, and the APEI code is
>> essentially a driver for some registers that reside there.  APEI is
>> the entity that manages those registers, and it needs to enforce
>> mutual exclusion so nobody else touches them behind its back, so I
>> think it makes sense for it to request the register regions and mark
>> them busy.
>>
>> My proposal is to change e820 so it either leaves ACPI NVS out of the
>> iomem_resource tree or puts it in but leaves it non-busy.
> 
> assume Huang Ying only tested with UEFI native boot?

No.  I tested it with legacy BIOS.  But ACPI NVS is not used by APEI on
my testing machine.

> i have one local patch for legacy mode booting, and it's similar to
> what Bjorn suggested.
> 
> Please check the attached patch.

I think we need help from ACPI guys on why ACPI NVS is marked as busy.

If my understanding were correct, ACPI NVS should not be used by OS at
all, so it is marked as busy.  But for APEI, Linux interprets some code
(instructions in ERST/EINJ table) from firmware.  I think this is
similar with AML code accessing ACPI NVS.

Hi, Len,

Do you think my understanding is correct?

Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/