From: Tomasz Nowicki <tomasz.nowicki@linaro.org>
To: rjw@rjwysocki.net, lenb@kernel.org, tony.luck@intel.com,
bp@alien8.de, m.chehab@samsung.com, bp@suse.de
Cc: linux-edac@vger.kernel.org, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-acpi@lists.linaro.org
Subject: Re: [PATCH v2 0/5] APEI: Make APEI architecture independent.
Date: Thu, 12 Jun 2014 10:34:23 +0200 [thread overview]
Message-ID: <5399660F.1020800@linaro.org> (raw)
In-Reply-To: <1401262770-25343-1-git-send-email-tomasz.nowicki@linaro.org>
Hi,
I would like to kindly remind and request for comments on this patches.
Regards,
Tomasz
On 28.05.2014 09:39, Tomasz Nowicki wrote:
> APEI is currently implemented so that it depends on x86 hardware.
> The primary dependency is that GHES uses the x86 NMI for hardware
> error notification and MCE for memory error handling. These patches
> remove that dependency.
>
> Other APEI features such as error reporting via external IRQ, error
> serialization, or error injection, do not require changes to use them
> on non-x86 architectures.
>
> The following patch set eliminates the APEI Kconfig x86 dependency
> by making these changes:
> - treat NMI notification as GHES feature - CONFIG_ACPI_APEI_NMI
> - reorganize GHES notification type init/deinitialization
> so that we can decide in run time whether NMI is supported or not
> - identify architectural boxes and abstract it accordingly (NMI and MCE)
> - rework ioremap for both IRQ and NMI context
>
> NMI code is kept in ghes.c file since NMI and IRQ context are tightly coupled.
>
> Note, these patches introduce no functional changes for x86. The NMI notification
> feature is selected for x86 by default. Architectures that want to use this
> feature should also provide NMI code infrastructure.
>
> V1->V2
> - address Borislav comment
> - abstract arch-specific calls instead of wrapping into the #ifdef
>
> Tomasz Nowicki (5):
> apei, mce: Factor out APEI architecture specific MCE calls.
> acpi, apei, ghes: Introduce ACPI_APEI_NMI to make NMI error
> notification a GHES feature.
> acpi, apei, ghes: Introduce more generic mechanism to init/deinit
> GHES error notifications.
> apei, ghes, nmi: Factor out NMI arch-specific calls.
> acpi, apei, ghes: Factor out ioremap virtual memory for IRQ and NMI
> context.
>
> arch/x86/kernel/acpi/Makefile | 1 +
> arch/x86/kernel/acpi/apei.c | 87 ++++++++++++
> drivers/acpi/apei/Kconfig | 10 +-
> drivers/acpi/apei/apei-base.c | 32 +++++
> drivers/acpi/apei/ghes.c | 301 +++++++++++++++++++++++++----------------
> drivers/acpi/apei/hest.c | 26 +---
> include/acpi/apei.h | 11 ++
> 7 files changed, 328 insertions(+), 140 deletions(-)
> create mode 100644 arch/x86/kernel/acpi/apei.c
>
prev parent reply other threads:[~2014-06-12 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 7:39 [PATCH v2 0/5] APEI: Make APEI architecture independent Tomasz Nowicki
2014-05-28 7:39 ` [PATCH v2 1/5] apei, mce: Factor out APEI architecture specific MCE calls Tomasz Nowicki
2014-06-12 10:23 ` Robert Richter
2014-06-12 13:07 ` Tomasz Nowicki
2014-05-28 7:39 ` [PATCH v2 2/5] acpi, apei, ghes: Introduce ACPI_APEI_NMI to make NMI error notification a GHES feature Tomasz Nowicki
2014-06-12 10:32 ` Robert Richter
2014-06-12 13:08 ` Tomasz Nowicki
2014-05-28 7:39 ` [PATCH v2 3/5] acpi, apei, ghes: Introduce more generic mechanism to init/deinit GHES error notifications Tomasz Nowicki
2014-05-28 7:39 ` [PATCH v2 4/5] apei, ghes, nmi: Factor out NMI arch-specific calls Tomasz Nowicki
2014-05-28 7:39 ` [PATCH v2 5/5] acpi, apei, ghes: Factor out ioremap virtual memory for IRQ and NMI context Tomasz Nowicki
2014-06-12 8:34 ` Tomasz Nowicki [this message]
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=5399660F.1020800@linaro.org \
--to=tomasz.nowicki@linaro.org \
--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-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.