From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM
Date: Mon, 12 Jan 2015 22:46:56 +0100 [thread overview]
Message-ID: <54B440D0.6090707@linaro.org> (raw)
In-Reply-To: <20141207093641.17563.84226.stgit@i3820>
Hi Nikolay,
looks good to me overall. A rebase on Christoffer's vgic init series and
Andre's v6 series will help in reviewing & testing.
Best Regards
Eric
On 12/07/2014 10:37 AM, Nikolay Nikolaev wrote:
> The IOEVENTFD KVM capability is a prerequisite for vhost support.
>
> This series enables the ioeventfd KVM capability on ARM.
>
> The implementation routes MMIO access in the IO abort handler to the KVM IO bus.
> If there is already a registered ioeventfd handler for this address, the file
> descriptor will be triggered.
>
> We extended the KVM IO bus API to expose the VCPU struct pointer. Now the VGIC
> MMIO access is done through this API. For this to operate the VGIC registers a
> kvm_io_device which represents the whole dist MMIO region.
>
> The patches are implemented on top of the latest Andre's vGICv3 work from here:
> http://www.linux-arm.org/git?p=linux-ap.git;a=shortlog;h=refs/heads/kvm-gicv3/v4
>
> The code was tested on Dual Cortex-A15 Exynos5250 (ARM Chromebook).
> ARM64 build was verified, but not run on actual HW.
>
> Changes since v1:
> - fixed x86 compilation
> - GICv3/GICv3 dist base selection
> - added vgic_unregister_kvm_io_dev to free the iodev resources
> - enable eventfd on ARM64
>
> ---
>
> Nikolay Nikolaev (5):
> KVM: Redesign kvm_io_bus_ API to pass VCPU structure to the callbacks.
> KVM: ARM: on IO mem abort - route the call to KVM MMIO bus
> KVM: ARM VGIC add kvm_io_bus_ frontend
> ARM/ARM64: enable linking against eventfd
> ARM: enable KVM_CAP_IOEVENTFD
>
>
> arch/arm/kvm/Kconfig | 1
> arch/arm/kvm/Makefile | 2 -
> arch/arm/kvm/arm.c | 3 +
> arch/arm/kvm/mmio.c | 32 +++++++++++
> arch/arm64/kvm/Kconfig | 1
> arch/arm64/kvm/Makefile | 2 -
> arch/ia64/kvm/kvm-ia64.c | 4 +
> arch/powerpc/kvm/mpic.c | 10 ++-
> arch/powerpc/kvm/powerpc.c | 4 +
> arch/s390/kvm/diag.c | 2 -
> arch/x86/kvm/i8254.c | 14 +++--
> arch/x86/kvm/i8259.c | 12 ++--
> arch/x86/kvm/lapic.c | 4 +
> arch/x86/kvm/vmx.c | 2 -
> arch/x86/kvm/x86.c | 13 ++---
> include/kvm/arm_vgic.h | 3 -
> include/linux/kvm_host.h | 10 ++-
> virt/kvm/arm/vgic.c | 127 +++++++++++++++++++++++++++++++++++++++++---
> virt/kvm/coalesced_mmio.c | 5 +-
> virt/kvm/eventfd.c | 4 +
> virt/kvm/ioapic.c | 8 +--
> virt/kvm/iodev.h | 23 +++++---
> virt/kvm/kvm_main.c | 32 ++++++-----
> 23 files changed, 237 insertions(+), 81 deletions(-)
>
> --
> Signature
>
next prev parent reply other threads:[~2015-01-12 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 9:37 [PATCH v2 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM Nikolay Nikolaev
2014-12-07 9:37 ` [PATCH v2 1/5] KVM: Redesign kvm_io_bus_ API to pass VCPU structure to the callbacks Nikolay Nikolaev
2015-01-12 17:10 ` Eric Auger
2014-12-07 9:37 ` [PATCH v2 2/5] KVM: ARM: on IO mem abort - route the call to KVM MMIO bus Nikolay Nikolaev
2015-01-12 17:09 ` Eric Auger
2015-01-12 17:48 ` Eric Auger
2015-01-24 1:02 ` Nikolay Nikolaev
2015-01-27 21:38 ` Christoffer Dall
2015-01-28 11:08 ` Eric Auger
2014-12-07 9:37 ` [PATCH v2 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend Nikolay Nikolaev
2015-01-12 21:41 ` Eric Auger
2015-01-24 0:57 ` Nikolay Nikolaev
2014-12-07 9:38 ` [PATCH v2 4/5] ARM/ARM64: enable linking against eventfd Nikolay Nikolaev
2014-12-07 9:38 ` [PATCH v2 5/5] ARM: enable KVM_CAP_IOEVENTFD Nikolay Nikolaev
2015-01-12 21:46 ` Eric Auger [this message]
[not found] ` <CADDJ2=M2UjsV0U9cFiRoKghWSckWje+h6M-XQ-0dqPrH3BXp1A@mail.gmail.com>
2015-01-15 15:31 ` [PATCH v2 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM Eric Auger
2015-01-15 19:47 ` 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=54B440D0.6090707@linaro.org \
--to=eric.auger@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).