From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756529AbaCZUhH (ORCPT ); Wed, 26 Mar 2014 16:37:07 -0400 Received: from mail.skyhub.de ([78.46.96.112]:45872 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755195AbaCZUhD (ORCPT ); Wed, 26 Mar 2014 16:37:03 -0400 Date: Wed, 26 Mar 2014 21:36:50 +0100 From: Borislav Petkov To: Mauro Carvalho Chehab , Tomasz Nowicki Cc: "Rafael J. Wysocki" , Len Brown , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linaro-acpi , Tony , Borislav Petkov , linux-edac@vger.kernel.org, x86@kernel.org Subject: Re: RFC: APEI hardware reduced profile Message-ID: <20140326203650.GA3933@nazgul.tnic> References: <5332C32A.5070301@linaro.org> <6220935.TPfvPdvLIs@vostro.rjw.lan> <20140326121047.65176d7e@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140326121047.65176d7e@samsung.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.