From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: RFC: APEI hardware reduced profile Date: Wed, 26 Mar 2014 15:55:07 +0100 Message-ID: <6220935.TPfvPdvLIs@vostro.rjw.lan> References: <5332C32A.5070301@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit Return-path: Received: from v094114.home.net.pl ([79.96.170.134]:53114 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753842AbaCZOko (ORCPT ); Wed, 26 Mar 2014 10:40:44 -0400 In-Reply-To: <5332C32A.5070301@linaro.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Tomasz Nowicki Cc: Len Brown , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linaro-acpi , Tony , Borislav Petkov , Borislav Petkov , Mauro Carvalho Chehab On Wednesday, March 26, 2014 01:08:10 PM Tomasz Nowicki wrote: > Hi, Hi, This is a question for Tony, Boris and Mauro (CCed now). > Currently APEI depends on x86 architecture. It is because of many x86 > specific features like "IA-32 Architecture Corrected Machine Check > " error source or NMI hardware error notification. However, many other > features like "PCI Express Device AER Structure" or GHES via external > interrupt can be still used perfectly by other architectures. So my idea > is to move x86 dependency away form Kconfig to APEI areas where it > really applies to. > > I have started refactoring ghes.c driver in that direction. And here > comes my confusion, how should we treat x86 related parts, as fixed > profile? (which means we could use ACPI_REDUCED_HARDWARE or > CONFIG_ACPI_REDUCED_HARDWARE_ONLY define). I would like to ask for your > opinion. Thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.