From: James Morse <james.morse at arm.com>
To: devel@acpica.org
Subject: Re: [Devel] [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8
Date: Wed, 18 Oct 2017 10:44:48 +0100 [thread overview]
Message-ID: <59E72290.6060604@arm.com> (raw)
In-Reply-To: 20171018092547.guf54e6aqbzzfxrq@pd.tnic
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Hi Borislav!
On 18/10/17 10:25, Borislav Petkov wrote:
> On Wed, Oct 18, 2017 at 05:17:27PM +0800, gengdongjiu wrote:
>> Thanks Borislav, can I write it as asynchronous exception or
>> asynchronous abort?
>
> WTF?!
Yup.
> The thing is abbreviated as "SEI" and apparently means "System Error
> Interrupt". Nothing else.
ARM has 'external abort', which are either synchronous or asynchronous, both are
delivered as different types of exception.
Asynchronous external abort is treated as a special kind of interrupt, 'SError
Interrupt', (where SError stands for System Error, but its rarely written like
that). 'SEI' is a relatively new abbreviation for SError interrupt.
What should we call this thing? In the ACPI code I'd prefer 'SEI' as that is
what the ACPI spec calls it. Here we are talking about an GHES notification.
But in the arm64 arch code this should be called SError Interrupt as this is
what the ARM-ARM calls it. This code cares about exception routing and interrupt
masking.
But, I don't really care.
Thanks,
James
WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com>
To: Borislav Petkov <bp@suse.de>
Cc: gengdongjiu <gengdongjiu@huawei.com>,
tbaicar@codeaurora.org, will.deacon@arm.com, rjw@rjwysocki.net,
lenb@kernel.org, robert.moore@intel.com, lv.zheng@intel.com,
mark.rutland@arm.com, kristina.martsenko@arm.com,
mingo@kernel.org, punit.agrawal@arm.com, stephen.boyd@linaro.org,
kamensky@cisco.com, prarit@redhat.com, shiju.jose@huawei.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
devel@acpica.org, Huangshaoyu <huangshaoyu@huawei.com>,
Wuquanming <wuquanming@huawei.com>
Subject: Re: [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8
Date: Wed, 18 Oct 2017 10:44:48 +0100 [thread overview]
Message-ID: <59E72290.6060604@arm.com> (raw)
In-Reply-To: <20171018092547.guf54e6aqbzzfxrq@pd.tnic>
Hi Borislav!
On 18/10/17 10:25, Borislav Petkov wrote:
> On Wed, Oct 18, 2017 at 05:17:27PM +0800, gengdongjiu wrote:
>> Thanks Borislav, can I write it as asynchronous exception or
>> asynchronous abort?
>
> WTF?!
Yup.
> The thing is abbreviated as "SEI" and apparently means "System Error
> Interrupt". Nothing else.
ARM has 'external abort', which are either synchronous or asynchronous, both are
delivered as different types of exception.
Asynchronous external abort is treated as a special kind of interrupt, 'SError
Interrupt', (where SError stands for System Error, but its rarely written like
that). 'SEI' is a relatively new abbreviation for SError interrupt.
What should we call this thing? In the ACPI code I'd prefer 'SEI' as that is
what the ACPI spec calls it. Here we are talking about an GHES notification.
But in the arm64 arch code this should be called SError Interrupt as this is
what the ARM-ARM calls it. This code cares about exception routing and interrupt
masking.
But, I don't really care.
Thanks,
James
WARNING: multiple messages have this Message-ID (diff)
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8
Date: Wed, 18 Oct 2017 10:44:48 +0100 [thread overview]
Message-ID: <59E72290.6060604@arm.com> (raw)
In-Reply-To: <20171018092547.guf54e6aqbzzfxrq@pd.tnic>
Hi Borislav!
On 18/10/17 10:25, Borislav Petkov wrote:
> On Wed, Oct 18, 2017 at 05:17:27PM +0800, gengdongjiu wrote:
>> Thanks Borislav, can I write it as asynchronous exception or
>> asynchronous abort?
>
> WTF?!
Yup.
> The thing is abbreviated as "SEI" and apparently means "System Error
> Interrupt". Nothing else.
ARM has 'external abort', which are either synchronous or asynchronous, both are
delivered as different types of exception.
Asynchronous external abort is treated as a special kind of interrupt, 'SError
Interrupt', (where SError stands for System Error, but its rarely written like
that). 'SEI' is a relatively new abbreviation for SError interrupt.
What should we call this thing? In the ACPI code I'd prefer 'SEI' as that is
what the ACPI spec calls it. Here we are talking about an GHES notification.
But in the arm64 arch code this should be called SError Interrupt as this is
what the ARM-ARM calls it. This code cares about exception routing and interrupt
masking.
But, I don't really care.
Thanks,
James
next prev reply other threads:[~2017-10-18 9:44 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 8:02 [PATCH v5 1/2] acpi: apei: remove the unused dead-code for SEA/NMI notification type Dongjiu Geng
2017-10-17 8:02 ` Dongjiu Geng
2017-10-17 8:02 ` Dongjiu Geng
2017-10-17 8:02 ` [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8 Dongjiu Geng
2017-10-17 8:02 ` Dongjiu Geng
2017-10-17 8:02 ` Dongjiu Geng
2017-10-17 17:06 ` Borislav Petkov
2017-10-17 17:06 ` Borislav Petkov
2017-10-18 5:00 ` [Devel] " gengdongjiu
2017-10-18 5:00 ` gengdongjiu
2017-10-18 5:00 ` gengdongjiu
2017-10-18 5:00 ` gengdongjiu
2017-10-18 9:06 ` Borislav Petkov
2017-10-18 9:06 ` Borislav Petkov
2017-10-18 9:17 ` [Devel] " gengdongjiu
2017-10-18 9:17 ` gengdongjiu
2017-10-18 9:17 ` gengdongjiu
2017-10-18 9:17 ` gengdongjiu
2017-10-18 9:25 ` Borislav Petkov
2017-10-18 9:25 ` Borislav Petkov
2017-10-18 9:44 ` James Morse [this message]
2017-10-18 9:44 ` James Morse
2017-10-18 9:44 ` James Morse
2017-10-18 10:04 ` Borislav Petkov
2017-10-18 10:04 ` Borislav Petkov
2017-10-17 14:06 ` [PATCH v5 1/2] acpi: apei: remove the unused dead-code for SEA/NMI notification type Tyler Baicar
2017-10-17 14:06 ` Tyler Baicar
2017-10-17 16:43 ` Borislav Petkov
2017-10-17 16:43 ` Borislav Petkov
2017-10-18 3:04 ` [Devel] " gengdongjiu
2017-10-18 3:04 ` gengdongjiu
2017-10-18 3:04 ` gengdongjiu
2017-10-18 3:04 ` gengdongjiu
2017-10-18 10:17 ` Borislav Petkov
2017-10-18 10:17 ` Borislav Petkov
2017-10-18 12:27 ` [Devel] " gengdongjiu
2017-10-18 12:27 ` gengdongjiu
2017-10-18 12:27 ` gengdongjiu
2017-10-18 12:27 ` gengdongjiu
2017-10-18 13:14 ` Borislav Petkov
2017-10-18 13:14 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2017-10-18 10:21 [Devel] [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8 gengdongjiu
2017-10-18 10:21 ` gengdongjiu
2017-10-18 10:21 ` gengdongjiu
2017-10-18 10:21 ` gengdongjiu
2017-10-18 10:25 [Devel] " gengdongjiu
2017-10-18 10:25 ` gengdongjiu
2017-10-18 10:25 ` gengdongjiu
2017-10-18 10:25 ` gengdongjiu
2017-10-18 10:26 [Devel] " James Morse
2017-10-18 10:26 ` James Morse
2017-10-18 10:26 ` James Morse
2017-10-18 11:39 [Devel] " gengdongjiu
2017-10-18 11:39 ` gengdongjiu
2017-10-18 11:39 ` gengdongjiu
2017-10-18 11:39 ` gengdongjiu
2017-10-18 15:04 [Devel] " gengdongjiu
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=59E72290.6060604@arm.com \
--to=devel@acpica.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.