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]

Message-ID: <4E5AEAF4.3000800@intel.com>
Date:	Mon, 29 Aug 2011 09:27:16 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
CC:	Pavel Ivanov <paivanof@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"Brown, Len" <len.brown@...el.com>
Subject: Re: APEI: Can not request iomem region for GARs

On 08/26/2011 09:43 PM, Bjorn Helgaas wrote:
> On Thu, Aug 25, 2011 at 10:13 PM, Huang Ying <ying.huang@...el.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.

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/