From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/4] vgic additions for forwarded irq
Date: Mon, 24 Nov 2014 11:50:37 +0100 [thread overview]
Message-ID: <20141124105037.GL3401@cbox> (raw)
In-Reply-To: <1416766373-13569-1-git-send-email-eric.auger@linaro.org>
On Sun, Nov 23, 2014 at 07:12:49PM +0100, Eric Auger wrote:
> This series applies on top of "ARM: Forwarding physical
> interrupts to a guest VM" (http://lwn.net/Articles/603514/)
> series.
Marc and Eric,
Does it make sense to review and look at these patches given the current
state of the forwarding patches, or should we wait until Marc respins
that series?
>
> It brings some extra functionalities that were requested to
> be able to inject virtual level sensitive IRQs triggered from
> VFIO/irqfd.
>
> It adds:
> - a specific handling of forwarded IRQ into the VGIC state machine.
> - deactivation of physical IRQ and unforwarding on vgic destruction
> - handling of forwarded IRQ injection before the vgic readiness:
> this was needed because in a sample qemu/vfio use case, qemu
> registers forwarded IRQ and set up VFIO signaling before the first
> vcpu run and hence before vgic readiness. At that time some
> physical IRQ may hit before the VGIC readiness. This is typically
> observed with Calxeda xgmac on second QEMU run.
this seems related to my note in the last patch? Same or different
problem?
-Christoffer
> - rbtree lock addition.
>
> Integrated pieces can be found at
> ssh://git.linaro.org/people/eric.auger/linux.git
> on branch irqfd_integ_v8
>
> The first 2 patch files were previously part of [RFC v2 0/9]
> KVM-VFIO IRQ forward control (https://lkml.org/lkml/2014/9/1/347).
>
>
> Eric Auger (4):
> KVM: arm: vgic: fix state machine for forwarded IRQ
> KVM: arm: vgic: add forwarded irq rbtree lock
> KVM: arm: vgic: cleanup forwarded IRQs on destroy
> KVM: arm: vgic: handle irqfd forwarded IRQ injection before vgic
> readiness
>
> include/kvm/arm_vgic.h | 1 +
> virt/kvm/arm/vgic.c | 128 +++++++++++++++++++++++++++++++++++++++++--------
> 2 files changed, 110 insertions(+), 19 deletions(-)
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-11-24 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 18:12 [RFC 0/4] vgic additions for forwarded irq Eric Auger
2014-11-23 18:12 ` [RFC 1/4] KVM: arm: vgic: fix state machine for forwarded IRQ Eric Auger
2014-11-23 18:12 ` [RFC 2/4] KVM: arm: vgic: add forwarded irq rbtree lock Eric Auger
2014-11-23 18:12 ` [RFC 3/4] KVM: arm: vgic: cleanup forwarded IRQs on destroy Eric Auger
2014-11-23 18:12 ` [RFC 4/4] KVM: arm: vgic: handle irqfd forwarded IRQ injection before vgic readiness Eric Auger
2014-11-24 10:50 ` Christoffer Dall [this message]
2014-11-24 10:54 ` [RFC 0/4] vgic additions for forwarded irq Marc Zyngier
2014-11-24 11:08 ` Eric Auger
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=20141124105037.GL3401@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).