From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: Julien Grall <julien.grall@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH-4.5 0/4] remove maintenance interrupts
Date: Fri, 07 Feb 2014 23:22:19 +0000 [thread overview]
Message-ID: <52F56AAB.7080300@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1402071847430.4373@kaball.uk.xensource.com>
On 07/02/14 18:56, Stefano Stabellini wrote:
> Hi all,
Hi Stefano,
> this patch series removes any needs for maintenance interrupts for both
> hardware and software interrupts in Xen.
> It achieves the goal by using the GICH_LR_HW bit for hardware interrupts
> and by checking the status of the GICH_LR registers on return to guest,
> clearing the registers that are invalid and handling the lifecycle of
> the corresponding interrupts in Xen data structures.
After reading your patch series I see a possible race condition with the
timer interrupt.
As you know, Xen can re-inject the timer interrupt before the previous
one is EOIed. As it's the timer, the IRQ is injected on the current
running VCPU.
vgic_vcpu_inject_irq(timer)
-> IRQ already visible to the guest -> set PENDING
return to guest context
<--------------------- Guest EOI the IRQ
.... few milleseconds
going to hyp mode
-> doing stuff
-> reinject the timer IRQ
If I'm not mistaken, with your solution, the next IRQ can be delayed for
few milliseconds. That could be fixed by updating the Lrs.
--
Julien Grall
next prev parent reply other threads:[~2014-02-07 23:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 18:56 [PATCH-4.5 0/4] remove maintenance interrupts Stefano Stabellini
2014-02-07 18:56 ` [PATCH-4.5 1/4] xen/arm: remove unused virtual parameter from vgic_vcpu_inject_irq Stefano Stabellini
2014-02-07 22:06 ` Julien Grall
2014-02-07 18:56 ` [PATCH-4.5 2/4] xen/arm: support HW interrupts in gic_set_lr Stefano Stabellini
2014-02-07 22:31 ` Julien Grall
2014-02-10 16:50 ` Stefano Stabellini
2014-02-07 18:56 ` [PATCH-4.5 3/4] xen/arm: do not request maintenance_interrupts Stefano Stabellini
2014-02-07 22:45 ` Julien Grall
2014-02-10 17:03 ` Stefano Stabellini
2014-02-10 17:21 ` Julien Grall
2014-02-07 23:10 ` Julien Grall
2014-02-10 17:06 ` Stefano Stabellini
2014-02-10 17:09 ` Ian Campbell
2014-02-10 17:16 ` Stefano Stabellini
2014-02-10 17:18 ` Ian Campbell
2014-02-10 17:24 ` Stefano Stabellini
2014-02-10 17:33 ` Ian Campbell
2014-02-10 17:11 ` Julien Grall
2014-02-07 18:56 ` [PATCH-4.5 4/4] xen/arm: set GICH_HCR_NPIE if all the LRs are in use Stefano Stabellini
2014-02-07 23:39 ` Julien Grall
2014-02-10 16:59 ` Stefano Stabellini
2014-02-10 17:14 ` Julien Grall
2014-02-10 17:16 ` Stefano Stabellini
2014-02-07 23:22 ` Julien Grall [this message]
2014-02-10 17:08 ` [PATCH-4.5 0/4] remove maintenance interrupts 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=52F56AAB.7080300@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).