[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6220935.TPfvPdvLIs@vostro.rjw.lan>
Date: Wed, 26 Mar 2014 15:55:07 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Tomasz Nowicki <tomasz.nowicki@...aro.org>
Cc: 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@...en8.de>,
Borislav Petkov <bp@...e.de>,
Mauro Carvalho Chehab <m.chehab@...sung.com>
Subject: Re: RFC: APEI hardware reduced profile
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.
--
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