From: Shannon Zhao <shannon.zhao@linaro.org>
To: xen-devel@lists.xen.org
Cc: julien.grall@arm.com, shannon.zhao@linaro.org,
stefano.stabellini@citrix.com, peter.huangpeng@huawei.com,
zhaoshenglong@huawei.com
Subject: [PATCH v7 20/22] xen/acpi: Fix event-channel interrupt when booting with ACPI
Date: Fri, 25 Mar 2016 21:48:53 +0800 [thread overview]
Message-ID: <1458913735-2678-21-git-send-email-shannon.zhao@linaro.org> (raw)
In-Reply-To: <1458913735-2678-1-git-send-email-shannon.zhao@linaro.org>
Store the event-channel interrupt number and flag in HVM parameter
HVM_PARAM_CALLBACK_IRQ. Then Dom0 could get it through hypercall
HVMOP_get_param.
Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
---
xen/arch/arm/domain_build.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index f004d92..d9bc3de 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -2047,6 +2047,7 @@ static void initrd_load(struct kernel_info *kinfo)
static void evtchn_fixup(struct domain *d, struct kernel_info *kinfo)
{
int res, node;
+ u64 val;
gic_interrupt_t intr;
/*
@@ -2062,6 +2063,19 @@ static void evtchn_fixup(struct domain *d, struct kernel_info *kinfo)
printk("Allocating PPI %u for event channel interrupt\n",
d->arch.evtchn_irq);
+ /* Set the value of domain param HVM_PARAM_CALLBACK_IRQ */
+ val = (u64)HVM_PARAM_CALLBACK_TYPE_PPI << 56;
+ val |= (2 << 8); /* Active-low level-sensitive */
+ val |= d->arch.evtchn_irq & 0xff;
+ d->arch.hvm_domain.params[HVM_PARAM_CALLBACK_IRQ] = val;
+
+ /*
+ * When booting Dom0 using ACPI, Dom0 can only get the event channel
+ * interrupt via hypercall.
+ */
+ if ( !acpi_disabled )
+ return;
+
/* Fix up "interrupts" in /hypervisor node */
node = fdt_path_offset(kinfo->fdt, "/hypervisor");
if ( node < 0 )
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-25 13:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 13:48 [PATCH v7 00/22] Prepare UEFI and ACPI tables for Dom0 on ARM64 Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 01/22] arm/acpi: Estimate memory required for acpi/efi tables Shannon Zhao
2016-03-26 13:02 ` Stefano Stabellini
2016-03-29 10:24 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 02/22] arm/acpi: Add a helper function to get the acpi table offset Shannon Zhao
2016-03-29 10:48 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 03/22] arm/acpi: Prepare FADT table for Dom0 Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 04/22] arm/gic: Add a new callback for creating MADT " Shannon Zhao
2016-03-29 12:47 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 05/22] arm/acpi: Prepare " Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 06/22] arm/acpi: Prepare STAO " Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 07/22] arm/acpi: Prepare XSDT " Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 08/22] arm/acpi: Prepare RSDP " Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 09/22] arm/p2m: Add helper functions to map memory regions Shannon Zhao
2016-03-29 12:49 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 10/22] arm/acpi: Map all other tables for Dom0 Shannon Zhao
2016-03-29 13:02 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 11/22] arm/acpi: Prepare EFI system table " Shannon Zhao
2016-03-29 14:54 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 12/22] arm/acpi: Prepare EFI memory descriptor " Shannon Zhao
2016-03-29 14:54 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 13/22] arm/acpi: Map the new created EFI and ACPI tables to Dom0 Shannon Zhao
2016-03-29 15:01 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 14/22] arm/acpi: Create min DT stub for Dom0 Shannon Zhao
2016-03-29 16:10 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 15/22] arm/acpi: Permit access all Xen unused SPIs " Shannon Zhao
2016-03-29 16:10 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 16/22] arm/acpi: Configure SPI interrupt type and route to Dom0 dynamically Shannon Zhao
2016-03-29 16:12 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 17/22] arm/gic: Add a new callback to deny Dom0 access to GIC regions Shannon Zhao
2016-03-26 13:04 ` Stefano Stabellini
2016-03-29 16:13 ` Julien Grall
2016-03-25 13:48 ` [PATCH v7 18/22] arm/acpi: Permit MMIO access of Xen unused devices for Dom0 Shannon Zhao
2016-03-25 13:48 ` [PATCH v7 19/22] hvm/params: Add a new delivery type for event-channel in HVM_PARAM_CALLBACK_IRQ Shannon Zhao
2016-03-29 16:16 ` Julien Grall
2016-03-25 13:48 ` Shannon Zhao [this message]
2016-03-29 16:16 ` [PATCH v7 20/22] xen/acpi: Fix event-channel interrupt when booting with ACPI Julien Grall
2016-03-25 13:48 ` [PATCH v7 21/22] xen/arm: Add a hypercall for device mmio mapping Shannon Zhao
2016-03-30 16:05 ` Konrad Rzeszutek Wilk
2016-03-30 16:07 ` Konrad Rzeszutek Wilk
2016-03-25 13:48 ` [PATCH v7 22/22] xen/arm64: Add ACPI support Shannon Zhao
2016-03-29 16:20 ` Julien Grall
2016-03-29 7:12 ` [PATCH v7 00/22] Prepare UEFI and ACPI tables for Dom0 on ARM64 Jan Beulich
2016-03-29 16:22 ` Julien Grall
2016-03-30 7:55 ` Jan Beulich
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=1458913735-2678-21-git-send-email-shannon.zhao@linaro.org \
--to=shannon.zhao@linaro.org \
--cc=julien.grall@arm.com \
--cc=peter.huangpeng@huawei.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@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).