| 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
| ||
|
Message-ID: <20140326203650.GA3933@nazgul.tnic> Date: Wed, 26 Mar 2014 21:36:50 +0100 From: Borislav Petkov <bp@...en8.de> To: Mauro Carvalho Chehab <m.chehab@...sung.com>, Tomasz Nowicki <tomasz.nowicki@...aro.org> Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>, Len Brown <lenb@...nel.org>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linaro-acpi <linaro-acpi@...ts.linaro.org>, Tony <tony.luck@...el.com>, Borislav Petkov <bp@...e.de>, linux-edac@...r.kernel.org, x86@...nel.org Subject: Re: RFC: APEI hardware reduced profile On Wed, Mar 26, 2014 at 12:10:47PM -0300, Mauro Carvalho Chehab wrote: > Yet, it would be better if you could be a little more specific about > what are your plans and what are the common/not-common features that > you're mapping. Well, I don't see anything x86-specific in ghes.c on a quick scan - just the GHES gunk itself, which is the spec. Which begs the question, how much of the APEI spec is ARM going to implement and if it is a subset, this definitely needs to be handled cleanly. Judging by your text, it seems like you want to ignore the correctable errors part...? So yes, Tomasz, you want to be much more specific here :-) Thanks. -- 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/
Powered by blists - more mailing lists