From: Guoheyi <guoheyi@huawei.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>,
qemu-devel@nongnu.org, Shannon Zhao <shannon.zhaosl@gmail.com>,
qemu-arm@nongnu.org, James Morse <james.morse@arm.com>,
wanghaibin.wang@huawei.com, Dave Martin <Dave.Martin@arm.com>
Subject: Re: [RFC v2 14/14] virt/acpi: add SDEI table if SDEI is enabled
Date: Mon, 18 Nov 2019 14:44:31 +0800 [thread overview]
Message-ID: <9f032ccc-ae43-3710-daa8-445c6069903e@huawei.com> (raw)
In-Reply-To: <20191112155253.543e15ad@redhat.com>
On 2019/11/12 22:52, Igor Mammedov wrote:
> On Tue, 5 Nov 2019 17:10:56 +0800
> Heyi Guo <guoheyi@huawei.com> wrote:
>
>> Add SDEI table if SDEI is enabled, so that guest OS can get aware and
>> utilize the interfaces.
>>
>> Signed-off-by: Heyi Guo <guoheyi@huawei.com>
>> Cc: Peter Maydell <peter.maydell@linaro.org>
>> Cc: Dave Martin <Dave.Martin@arm.com>
>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: James Morse <james.morse@arm.com>
>> Cc: Shannon Zhao <shannon.zhaosl@gmail.com>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>> Cc: Igor Mammedov <imammedo@redhat.com>
>> ---
>>
>> Notes:
>> v2:
>> - Drop SDEI table definition and add comments
>>
>> hw/arm/virt-acpi-build.c | 26 ++++++++++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>>
>> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
>> index 4cd50175e0..73d3f8cd15 100644
>> --- a/hw/arm/virt-acpi-build.c
>> +++ b/hw/arm/virt-acpi-build.c
>> @@ -32,6 +32,7 @@
>> #include "trace.h"
>> #include "hw/core/cpu.h"
>> #include "target/arm/cpu.h"
>> +#include "target/arm/sdei.h"
>> #include "hw/acpi/acpi-defs.h"
>> #include "hw/acpi/acpi.h"
>> #include "hw/nvram/fw_cfg.h"
>> @@ -475,6 +476,26 @@ build_iort(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
>> "IORT", table_data->len - iort_start, 0, NULL, NULL);
>> }
>>
>> +/*
>> + * ACPI spec 6.2 Software Delegated Exception Interface (SDEI).
>> + * (Revision 1.0)
>> + * "SDEI" was reserved in ACPI 6.2. See "Links to ACPI-Related Documents"
>> + * (http://uefi.org/acpi) under the heading "Software
>> + * Delegated Exceptions Interface." The definition is under
>> + * "10 Appendix C: ACPI table definitions for SDEI" in the linked document.
>> + *
>> + * This is a dummy table to expose platform SDEI capbility to OS.
>> + */
>> +static void
>> +build_sdei(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
>> +{
>> + int sdei_start = table_data->len;
>> +
>> + (void)acpi_data_push(table_data, sizeof(AcpiTableHeader));
>> + build_header(linker, table_data, (void *)(table_data->data + sdei_start),
>> + "SDEI", table_data->len - sdei_start, 1, NULL, NULL);
>> +}
>> +
>> static void
>> build_spcr(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
>> {
>> @@ -825,6 +846,11 @@ void virt_acpi_build(VirtMachineState *vms, AcpiBuildTables *tables)
>> acpi_add_table(table_offsets, tables_blob);
>> build_spcr(tables_blob, tables->linker, vms);
>>
>> + if (sdei_enabled) {
> globals shouldn't be introduced in new code
OK. For this feature depends on KVM, does it make sense to add a flag to
struct VirtMachineState?
Thanks,
HG
>
>> + acpi_add_table(table_offsets, tables_blob);
>> + build_sdei(tables_blob, tables->linker, vms);
>> + }
>> +
>> if (ms->numa_state->num_nodes > 0) {
>> acpi_add_table(table_offsets, tables_blob);
>> build_srat(tables_blob, tables->linker, vms);
>
> .
>
next prev parent reply other threads:[~2019-11-18 6:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:10 [RFC v2 00/14] Add SDEI support for arm64 Heyi Guo
2019-11-05 9:10 ` [RFC v2 01/14] update-linux-headers.sh: import linux/arm_sdei.h to standard-headers Heyi Guo
2019-11-05 9:10 ` [RFC v2 02/14] standard-headers: import arm_sdei.h Heyi Guo
2019-11-06 17:52 ` Cornelia Huck
2019-11-07 1:40 ` Guoheyi
2019-11-07 8:50 ` Cornelia Huck
2019-11-07 8:55 ` Michael S. Tsirkin
2019-11-05 9:10 ` [RFC v2 03/14] arm/sdei: add virtual device framework Heyi Guo
2019-11-05 9:10 ` [RFC v2 04/14] arm: add CONFIG_SDEI build flag Heyi Guo
2019-11-05 9:10 ` [RFC v2 05/14] arm/sdei: add support to handle SDEI requests from guest Heyi Guo
2019-11-05 9:10 ` [RFC v2 06/14] arm/sdei: add system reset callback Heyi Guo
2019-11-05 9:10 ` [RFC v2 07/14] arm/sdei: add support to trigger event by GIC interrupt ID Heyi Guo
2019-11-05 9:10 ` [RFC v2 08/14] core/irq: add qemu_irq_remove_intercept interface Heyi Guo
2019-11-05 9:10 ` [RFC v2 09/14] arm/sdei: override qemu_irq handler when binding interrupt Heyi Guo
2019-11-05 9:10 ` [RFC v2 10/14] arm/sdei: add support to register interrupt bind notifier Heyi Guo
2019-11-05 9:10 ` [RFC v2 11/14] linux-headers/kvm.h: add capability to forward hypercall Heyi Guo
2019-11-06 17:55 ` Cornelia Huck
2019-11-07 1:44 ` Guoheyi
2019-11-07 8:57 ` Michael S. Tsirkin
2019-11-07 11:57 ` Guoheyi
2019-11-07 12:12 ` Cornelia Huck
2019-11-08 1:54 ` Guoheyi
2019-11-05 9:10 ` [RFC v2 12/14] arm/sdei: add stub to fix build failure when SDEI is not enabled Heyi Guo
2019-11-05 9:10 ` [RFC v2 13/14] arm/kvm: handle guest exit of hypercall Heyi Guo
2019-11-05 9:10 ` [RFC v2 14/14] virt/acpi: add SDEI table if SDEI is enabled Heyi Guo
2019-11-12 14:52 ` Igor Mammedov
2019-11-18 6:44 ` Guoheyi [this message]
2019-11-05 9:15 ` [RFC v2 00/14] Add SDEI support for arm64 Guoheyi
2019-11-05 9:36 ` no-reply
2019-11-05 9:38 ` no-reply
2019-11-18 6:55 ` Guoheyi
2019-11-18 13:35 ` Peter Maydell
2019-11-18 14:04 ` Guoheyi
2019-12-20 13:44 ` Peter Maydell
2019-12-23 8:20 ` Guoheyi
2020-02-04 8:26 ` Heyi Guo
2020-02-05 13:15 ` Marc Zyngier
2020-02-06 1:20 ` Heyi Guo
2020-02-06 17:30 ` Marc Zyngier
2020-02-07 10:52 ` James Morse
2020-02-07 11:08 ` Peter Maydell
2020-02-07 13:45 ` Heyi Guo
2020-02-07 13:17 ` Heyi Guo
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=9f032ccc-ae43-3710-daa8-445c6069903e@huawei.com \
--to=guoheyi@huawei.com \
--cc=Dave.Martin@arm.com \
--cc=imammedo@redhat.com \
--cc=james.morse@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.com \
--cc=wanghaibin.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).