linux-kernel - Re: Fwd: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode

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] [day] [month] [year] [list]

Message-ID: <20091009143133.GC19218@mock.linuxdev.us.dell.com>
Date:	Fri, 9 Oct 2009 09:31:33 -0500
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Huang Ying <ying.huang@...el.com>
Cc:	linux-pci@...r.kernel.org, linux-acpi@...r.kernel.org,
	Tom Long Nguyen <tom.l.nguyen@...el.com>,
	Zhang Yanmin <yanmin.zhang@...el.com>,
	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>
Subject: Re: Fwd: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode

On Fri, Oct 09, 2009 at 01:55:27PM +0800, Huang Ying wrote:
> Can you tell me where can I find more about PECI? Or you mean APEI (ACPI
> Platform Error Interfaces)?

Yes, APEI.  My mistake.  Too many acronyms for my little mind.

> We are working on APEI supporting now too, mainly on the general part.
> We will release the code after it passes our internal testing.

Excellent.  If you could post even the untested code, that would be
helpful. Do you have a timeline for publication?

My patch is fundamentally in response to the fact that your APEI code
is not present yet, and there is a problem seen at customer sites now
(particularly SLES 11, as that's the only "Enterprise"-class distro
version with the AER driver, but also any distro or kernel build that
includes the AER driver).  But without knowing when the rest of the
APEI code will land in mainline, I feel it would be safe to do the
minimum amount of HEST parsing, just enough to know if AER should be
disabled or not.  My patch can be considered "throw-away" code - to be
dropped when your APEI code lands in mainline and the distros.

> As H.Seto said, HEST table parsing code should go the general APEI
> supporting code. We have some HEST table parsing code, hope that can be
> used by your code too.

I agree completely.  But I need a solution in the short-term, both for
mainline and which can be backported, until your code is available.

I'm reworking my patch based on Seto-san's comments, and will repost
soon as linux-next stops crashing on me. :-)

Thanks,
Matt

-- 
Matt Domsch
Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
--
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/