From: Shannon Zhao <zhaoshenglong@huawei.com>
To: gengdongjiu <gengdongjiu@huawei.com>,
lersek@redhat.com, mst@redhat.com, imammedo@redhat.com,
peter.maydell@linaro.org, pbonzini@redhat.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org, kvm@vger.kernel.org,
edk2-devel@lists.01.org, christoffer.dall@linaro.org,
marc.zyngier@arm.com, will.deacon@arm.com, james.morse@arm.com,
tbaicar@codeaurora.org, ard.biesheuvel@linaro.org,
mingo@kernel.org, bp@suse.de, shiju.jose@huawei.com,
zjzhang@codeaurora.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, devel@acpica.org,
john.garry@huawei.com, jonathan.cameron@huawei.com,
shameerali.kolothum.thodi@huawei.com, huangdaode@hisilicon.com,
wangzhou1@hisilicon.com
Cc: huangshaoyu@huawei.com, wuquanming@huawei.com,
linuxarm@huawei.com, zhengqiang10@huawei.com
Subject: Re: [Qemu-devel] [PATCH v11 1/6] ACPI: add APEI/HEST/CPER structures and macros
Date: Sat, 26 Aug 2017 09:00:03 +0800 [thread overview]
Message-ID: <59A0C813.2060201@huawei.com> (raw)
In-Reply-To: <69090a96-ce90-4b2b-a419-c8d847d56093@huawei.com>
On 2017/8/25 18:37, gengdongjiu wrote:
>>> +
>>> >> +/* From the ACPI 6.1 spec, "18.3.2.9 Hardware Error Notification" */
>>> >> +
>> > It's better to refer to the first spec version of this structure and
>> > same with others you define.
> do you mean which spec version? the definition is aligned with the linux kernel.
What I mean here is that it's better to refer to the ACPI spec version
which introduces Hardware Error Notification first time.
>> >
>>> >> +enum AcpiHestNotifyType {
>>> >> + ACPI_HEST_NOTIFY_POLLED = 0,
>>> >> + ACPI_HEST_NOTIFY_EXTERNAL = 1,
>>> >> + ACPI_HEST_NOTIFY_LOCAL = 2,
>>> >> + ACPI_HEST_NOTIFY_SCI = 3,
>>> >> + ACPI_HEST_NOTIFY_NMI = 4,
>>> >> + ACPI_HEST_NOTIFY_CMCI = 5, /* ACPI 5.0 */
>>> >> + ACPI_HEST_NOTIFY_MCE = 6, /* ACPI 5.0 */
>>> >> + ACPI_HEST_NOTIFY_GPIO = 7, /* ACPI 6.0 */
>>> >> + ACPI_HEST_NOTIFY_SEA = 8, /* ACPI 6.1 */
>>> >> + ACPI_HEST_NOTIFY_SEI = 9, /* ACPI 6.1 */
>>> >> + ACPI_HEST_NOTIFY_GSIV = 10, /* ACPI 6.1 */
>>> >> + ACPI_HEST_NOTIFY_RESERVED = 11 /* 11 and greater are reserved */
>> > In ACPI 6.2, 11 is for Software Delegated Exception, is this useful for
>> > your patchset?
> it is usefull, for all the error source, I reserved the space for them.
> Because the space is allocated one time, is not dynamically allocated.
> so I use the ACPI_HEST_NOTIFY_RESERVED to specify that there is 11 error source.
>
I mean whether the new type Software Delegated Exception is useful for
RAS. If so, we could add this new type here.
Thanks,
--
Shannon
next prev parent reply other threads:[~2017-08-26 1:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 14:23 [Qemu-devel] [PATCH v11 0/6] Add RAS virtualization support for armv8 SEA and SEI Dongjiu Geng
2017-08-18 14:21 ` no-reply
2017-08-18 14:23 ` [Qemu-devel] [PATCH v11 1/6] ACPI: add APEI/HEST/CPER structures and macros Dongjiu Geng
2017-08-24 12:33 ` Shannon Zhao
2017-08-25 10:37 ` gengdongjiu
2017-08-26 1:00 ` Shannon Zhao [this message]
2017-08-26 1:45 ` gengdongjiu
2017-08-18 14:23 ` [Qemu-devel] [PATCH v11 2/6] ACPI: Add APEI GHES Table Generation support Dongjiu Geng
2017-08-24 13:03 ` Shannon Zhao
2017-08-25 11:20 ` gengdongjiu
2017-08-26 1:08 ` Shannon Zhao
2017-08-26 2:49 ` gengdongjiu
2017-08-29 10:20 ` Igor Mammedov
2017-08-29 11:15 ` gengdongjiu
2017-09-01 9:58 ` gengdongjiu
2017-09-01 11:51 ` Igor Mammedov
2017-08-18 14:23 ` [Qemu-devel] [PATCH v11 3/6] ACPI: build and enable APEI GHES in the Makefile and configuration Dongjiu Geng
2017-08-24 13:04 ` Shannon Zhao
2017-08-25 11:20 ` gengdongjiu
2017-08-18 14:23 ` [Qemu-devel] [PATCH v11 4/6] target-arm: kvm64: detect guest RAS EXTENSION feature Dongjiu Geng
2017-09-05 17:26 ` Peter Maydell
2017-09-06 9:35 ` gengdongjiu
2017-08-18 14:23 ` [Qemu-devel] [PATCH v11 5/6] target-arm: kvm64: handle SIGBUS signal for synchronous External Abort Dongjiu Geng
2017-09-05 17:46 ` Peter Maydell
2017-08-18 14:23 ` [Qemu-devel] [PATCH v11 6/6] target-arm: kvm64: Handle SError interrupt for the guest OS Dongjiu Geng
2017-09-05 17:50 ` Peter Maydell
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=59A0C813.2060201@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=devel@acpica.org \
--cc=edk2-devel@lists.01.org \
--cc=gengdongjiu@huawei.com \
--cc=huangdaode@hisilicon.com \
--cc=huangshaoyu@huawei.com \
--cc=imammedo@redhat.com \
--cc=james.morse@arm.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lersek@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=wangzhou1@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=wuquanming@huawei.com \
--cc=zhengqiang10@huawei.com \
--cc=zjzhang@codeaurora.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;
as well as URLs for NNTP newsgroup(s).