From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tomasz Nowicki <tomasz.nowicki@linaro.org>
Cc: Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linaro-acpi <linaro-acpi@lists.linaro.org>,
Tony <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
Borislav Petkov <bp@suse.de>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: RFC: APEI hardware reduced profile
Date: Wed, 26 Mar 2014 15:55:07 +0100 [thread overview]
Message-ID: <6220935.TPfvPdvLIs@vostro.rjw.lan> (raw)
In-Reply-To: <5332C32A.5070301@linaro.org>
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.
next prev parent reply other threads:[~2014-03-26 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 12:08 RFC: APEI hardware reduced profile Tomasz Nowicki
2014-03-26 14:55 ` Rafael J. Wysocki [this message]
2014-03-26 15:10 ` Mauro Carvalho Chehab
2014-03-26 20:36 ` Borislav Petkov
2014-03-27 9:17 ` Tomasz Nowicki
2014-03-27 9:05 ` Tomasz Nowicki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6220935.TPfvPdvLIs@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=lenb@kernel.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=tomasz.nowicki@linaro.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox