From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: christoffer.dall@linaro.org, xen-devel@lists.xenproject.org,
tim@xen.org, parth.dixit@linaro.org,
stefano.stabellini@citrix.com
Subject: Re: [PATCH for-4.6 3/4] xen/arm: vgic: notice if the vIRQ is not allocated when the guest enable it
Date: Tue, 13 Jan 2015 15:55:00 +0000 [thread overview]
Message-ID: <1421164500.19103.132.camel@citrix.com> (raw)
In-Reply-To: <1418395392-30460-4-git-send-email-julien.grall@linaro.org>
On Fri, 2014-12-12 at 14:43 +0000, Julien Grall wrote:
> This help for guest interrupts debugging. If the vIRQ is not allocate,
> this means that nothing is wired to it.
Should we short circuit the rest of the enable operation for this IRQ
then? i.e. implement such writes as ignored, e.g. not reflect it in
reads of ISENABLER etc.
What (if anything) does the GIC spec have to say on the subject?
> Signed-off-by: Julien Grall <julien.grall@linaro.org>
> ---
> xen/arch/arm/vgic.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/xen/arch/arm/vgic.c b/xen/arch/arm/vgic.c
> index dbfc259..719cb9f 100644
> --- a/xen/arch/arm/vgic.c
> +++ b/xen/arch/arm/vgic.c
> @@ -282,6 +282,10 @@ void vgic_enable_irqs(struct vcpu *v, uint32_t r, int n)
> if ( !list_empty(&p->inflight) && !test_bit(GIC_IRQ_GUEST_VISIBLE, &p->status) )
> gic_raise_guest_irq(v_target, irq, p->priority);
> spin_unlock_irqrestore(&v_target->arch.vgic.lock, flags);
> +
> + if ( !test_bit(irq, d->arch.vgic.allocated_irqs) )
> + gdprintk(XENLOG_DEBUG, "vIRQ %u is not allocated\n", irq);
Should this not be first after the irq= line inside this loop?
> +
> if ( p->desc != NULL )
> {
> irq_set_affinity(p->desc, cpumask_of(v_target->processor));
next prev parent reply other threads:[~2015-01-13 15:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 14:43 [PATCH for-4.6 0/4] Find automatically a PPI for the DOM0 even channel IRQ Julien Grall
2014-12-12 14:43 ` [PATCH for-4.6 1/4] xen/arm: vgic: Rename nr_lines into nr_spis Julien Grall
2015-01-13 15:38 ` Ian Campbell
2015-01-13 15:52 ` Julien Grall
2015-01-13 15:59 ` Ian Campbell
2014-12-12 14:43 ` [PATCH for-4.6 2/4] xen/arm: vgic: Keep track of vIRQ used by a domain Julien Grall
2014-12-15 15:32 ` Stefano Stabellini
2014-12-15 16:07 ` Julien Grall
2014-12-17 15:23 ` Julien Grall
2015-01-13 15:51 ` Ian Campbell
2015-01-13 16:27 ` Julien Grall
2015-01-13 16:46 ` Ian Campbell
2015-01-13 16:57 ` Julien Grall
2015-01-13 17:18 ` Ian Campbell
2015-01-13 17:35 ` Julien Grall
2015-01-13 17:22 ` Julien Grall
2015-01-13 17:34 ` Julien Grall
2014-12-12 14:43 ` [PATCH for-4.6 3/4] xen/arm: vgic: notice if the vIRQ is not allocated when the guest enable it Julien Grall
2015-01-13 15:55 ` Ian Campbell [this message]
2015-01-13 20:33 ` Julien Grall
2015-01-14 12:28 ` Ian Campbell
2015-01-14 12:42 ` Julien Grall
2015-01-15 13:27 ` Julien Grall
2015-01-15 13:31 ` Ian Campbell
2014-12-12 14:43 ` [PATCH for-4.6 4/4] xen/arm: Find automatically a PPI for the DOM0 event channel interrupt Julien Grall
2014-12-12 17:00 ` Julien Grall
2014-12-15 15:35 ` Stefano Stabellini
2014-12-15 16:09 ` Julien Grall
2015-01-13 15:58 ` Ian Campbell
2015-01-14 12:24 ` Julien Grall
2015-01-14 12:30 ` Ian Campbell
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=1421164500.19103.132.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=christoffer.dall@linaro.org \
--cc=julien.grall@linaro.org \
--cc=parth.dixit@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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.