From: Julien Grall <julien.grall@arm.com>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, steve.capper@arm.com,
Julien Grall <julien.grall@arm.com>,
shannon.zhao@linaro.org, shankerd@codeaurora.org,
wei.chen@linaro.org
Subject: [PATCH v3 6/9] Revert "xen/arm: warn the user that we cannot route SPIs to Dom0 on ACPI"
Date: Wed, 27 Jul 2016 14:58:27 +0100 [thread overview]
Message-ID: <1469627910-3902-7-git-send-email-julien.grall@arm.com> (raw)
In-Reply-To: <1469627910-3902-1-git-send-email-julien.grall@arm.com>
This reverts commit f91c84edebe67296e4051af055dbf0adafb13a37. SPI
routing for ACPI support will be added in a follow-up patch.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
---
Changes in v3:
- Fix typo in Stefano's e-mail address
Changes in v2:
- Add Stefano's reviewed-by
---
xen/arch/arm/vgic.c | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/xen/arch/arm/vgic.c b/xen/arch/arm/vgic.c
index e47daca..938bc7d 100644
--- a/xen/arch/arm/vgic.c
+++ b/xen/arch/arm/vgic.c
@@ -25,8 +25,6 @@
#include <xen/irq.h>
#include <xen/sched.h>
#include <xen/perfc.h>
-#include <xen/iocap.h>
-#include <xen/acpi.h>
#include <asm/current.h>
@@ -350,22 +348,9 @@ void vgic_enable_irqs(struct vcpu *v, uint32_t r, int n)
unsigned long flags;
int i = 0;
struct vcpu *v_target;
- struct domain *d = v->domain;
while ( (i = find_next_bit(&mask, 32, i)) < 32 ) {
irq = i + (32 * n);
- /* Set the irq type and route it to guest only for SPI and Dom0 */
- if( irq_access_permitted(d, irq) && is_hardware_domain(d) &&
- ( irq >= 32 ) && ( !acpi_disabled ) )
- {
- static int log_once = 0;
- if ( !log_once )
- {
- gprintk(XENLOG_WARNING, "Routing SPIs to Dom0 on ACPI systems is unimplemented.\n");
- log_once++;
- }
- }
-
v_target = __vgic_get_target_vcpu(v, irq);
p = irq_to_pending(v_target, irq);
set_bit(GIC_IRQ_GUEST_ENABLED, &p->status);
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-27 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 13:58 [PATCH v3 0/9] xen/arm: Support SPIs routing Julien Grall
2016-07-27 13:58 ` [PATCH v3 1/9] xen/arm: gic: Consolidate the IRQ affinity set in a single place Julien Grall
2016-07-27 13:58 ` [PATCH v3 2/9] xen/arm: gic: Do not configure affinity during routing Julien Grall
2016-07-27 13:58 ` [PATCH v3 3/9] xen/arm: gic: split set_irq_properties Julien Grall
2016-07-27 13:58 ` [PATCH v3 4/9] xen/arm: gic: set_type: Pass the type in parameter rather than in desc->arch.type Julien Grall
2016-07-27 13:58 ` [PATCH v3 5/9] xen/arm: gic: Document how gic_set_irq_type should be called Julien Grall
2016-07-27 13:58 ` Julien Grall [this message]
2016-07-27 13:58 ` [PATCH v3 7/9] xen/arm: Allow DOM0 to set the IRQ type Julien Grall
2016-07-27 19:22 ` Stefano Stabellini
2016-07-27 13:58 ` [PATCH v3 8/9] xen/arm: acpi: route all unused IRQs to DOM0 Julien Grall
2016-07-27 13:58 ` [PATCH v3 9/9] xen/arm: Fix coding style and update comment in acpi_route_spis Julien Grall
2016-07-27 19:27 ` [PATCH v3 0/9] xen/arm: Support SPIs routing Stefano Stabellini
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=1469627910-3902-7-git-send-email-julien.grall@arm.com \
--to=julien.grall@arm.com \
--cc=shankerd@codeaurora.org \
--cc=shannon.zhao@linaro.org \
--cc=sstabellini@kernel.org \
--cc=steve.capper@arm.com \
--cc=wei.chen@linaro.org \
--cc=xen-devel@lists.xen.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).