From: Tomasz Nowicki <tomasz.nowicki@linaro.org>
To: Tony Luck <tony.luck@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Borislav Petkov <bp@alien8.de>,
"m.chehab@samsung.com" <m.chehab@samsung.com>,
Borislav Petkov <bp@suse.de>,
rric@kernel.org,
Linux Edac Mailing List <linux-edac@vger.kernel.org>,
X86-ML <x86@kernel.org>, linux-acpi <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linaro-acpi@lists.linaro.org
Subject: Re: [PATCH v5 0/3] APEI: Make APEI architecture independent.
Date: Wed, 23 Jul 2014 09:40:44 +0200 [thread overview]
Message-ID: <53CF66FC.1040604@linaro.org> (raw)
In-Reply-To: <CA+8MBb+KuKaeXr5p97xWZKJB7T-NAooi-kXQTaPx0QnO53-oCQ@mail.gmail.com>
Many thanks Tony! And thanks goes to Borislav and Robert too.
Regards,
Tomasz
On 22.07.2014 23:08, Tony Luck wrote:
> On Tue, Jul 22, 2014 at 2:20 AM, Tomasz Nowicki
> <tomasz.nowicki@linaro.org> 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 architecture - HAVE_ACPI_APEI_NMI
>> - group and wrap around #ifdef CONFIG_HAVE_ACPI_APEI_NMI code which
>> is used only for NMI path
>> - identify architectural boxes and abstract it accordingly (tlb flush 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 hard selected for x86. Architectures that want to use this
>> feature should also provide NMI code infrastructure.
>
> Looks OK to me. I've thrown this series into a topic branch of the ras
> git tree named "apei". When I push it to kernel.org in a few minutes
> the build test robots will pounce and try all sorts of randconfig builds.
> They'll send you (and me) e-mails if they find any corner cases.
>
> -Tony
>
prev parent reply other threads:[~2014-07-23 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 9:20 [PATCH v5 0/3] APEI: Make APEI architecture independent Tomasz Nowicki
2014-07-22 9:20 ` [PATCH v5 1/3] apei, mce: Factor out APEI architecture specific MCE calls Tomasz Nowicki
2014-07-22 9:20 ` [PATCH v5 2/3] acpi, apei, ghes: Make NMI error notification to be GHES architecture extension Tomasz Nowicki
2014-07-22 16:57 ` Borislav Petkov
2014-07-22 9:20 ` [PATCH v5 3/3] acpi, apei, ghes: Factor out ioremap virtual memory for IRQ and NMI context Tomasz Nowicki
2014-07-22 21:08 ` [PATCH v5 0/3] APEI: Make APEI architecture independent Tony Luck
2014-07-23 7:40 ` 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=53CF66FC.1040604@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=rric@kernel.org \
--cc=tony.luck@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox