From: Christoffer Dall <cdall@linaro.org>
To: kvmarm@lists.cs.columbia.edu, Eric Auger <eric.auger@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
Christoffer Dall <cdall@linaro.org>
Subject: [PATCH v2 0/6] Handle forwarded level-triggered interrupts
Date: Mon, 4 Sep 2017 12:24:50 +0200 [thread overview]
Message-ID: <20170904102456.9025-1-cdall@linaro.org> (raw)
This series illustrates an alternative approach to Eric Auger's direct EOI
setup patches [1] in terms of the KVM VGIC support.
The idea is to maintain existing semantics for the VGIC for mapped
level-triggered IRQs and think support for the timer into it.
Patch 1 is necessary to align the timer and VFIO ways of signaling the
VGIC. Patch 2 is stolen from Eric's series and is necessary for these
patches to compile as well. Patch 3 includes the core support for
mapped level-triggered interrupts. Patch 4 handles guest MMIO acess to
the virtual distributor. Patch 5 moves some code around for patch 6.
Patch 6 implements an optimization for the timer. The last two patches
could be deferred until the timer optimization series.
Based on v4.13-rc7.
Thanks,
-Christoffer
Changes since v1:
- Added necessary changes to the timer (Patch 1)
- Added handling of guest MMIO accesses to the virtual distributor
(Patch 4)
- Addressed Marc's comments from the initial RFC (mostly renames)
Christoffer Dall (5):
KVM: arm/arm64: Don't cache the timer IRQ level
KVM: arm/arm64: vgic: Support level-triggered mapped interrupts
KVM: arm/arm64: Support VGIC dist pend/active changes for mapped IRQs
KVM: arm/arm64: Rearrange kvm_vgic_[un]map_phys code in vgic.c
KVM: arm/arm64: Provide a vgic interrupt line level sample function
Eric Auger (1):
KVM: arm/arm64: vgic: restructure kvm_vgic_(un)map_phys_irq
include/kvm/arm_vgic.h | 19 +++++++++--
virt/kvm/arm/arch_timer.c | 52 +++++++++++++-----------------
virt/kvm/arm/vgic/vgic-mmio.c | 27 ++++++++++++++++
virt/kvm/arm/vgic/vgic-v2.c | 29 +++++++++++++++++
virt/kvm/arm/vgic/vgic-v3.c | 29 +++++++++++++++++
virt/kvm/arm/vgic/vgic.c | 75 ++++++++++++++++++++++++++++++++++++-------
virt/kvm/arm/vgic/vgic.h | 8 +++++
7 files changed, 196 insertions(+), 43 deletions(-)
--
2.9.0
next reply other threads:[~2017-09-04 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 10:24 Christoffer Dall [this message]
2017-09-04 10:24 ` [PATCH v2 1/6] KVM: arm/arm64: Don't cache the timer IRQ level Christoffer Dall
2017-09-04 10:24 ` [PATCH v2 2/6] KVM: arm/arm64: vgic: restructure kvm_vgic_(un)map_phys_irq Christoffer Dall
2017-09-04 10:24 ` [PATCH v2 3/6] KVM: arm/arm64: vgic: Support level-triggered mapped interrupts Christoffer Dall
2017-09-05 9:38 ` Auger Eric
2017-09-05 13:57 ` Christoffer Dall
2017-09-04 10:24 ` [PATCH v2 4/6] KVM: arm/arm64: Support VGIC dist pend/active changes for mapped IRQs Christoffer Dall
2017-09-04 10:24 ` [PATCH v2 5/6] KVM: arm/arm64: Rearrange kvm_vgic_[un]map_phys code in vgic.c Christoffer Dall
2017-09-05 10:26 ` Auger Eric
2017-09-05 14:00 ` Christoffer Dall
2017-09-05 14:49 ` Auger Eric
2017-09-04 10:24 ` [PATCH v2 6/6] KVM: arm/arm64: Provide a vgic interrupt line level sample function Christoffer Dall
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=20170904102456.9025-1-cdall@linaro.org \
--to=cdall@linaro.org \
--cc=andre.przywara@arm.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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