From: Pavel Fedin <p.fedin@samsung.com>
To: kvm@vger.kernel.org
Cc: Christoffer Dall <christoffer.dall@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
Pavel Fedin <p.fedin@samsung.com>
Subject: [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation
Date: Mon, 29 Jun 2015 12:53:46 +0300 [thread overview]
Message-ID: <cover.1435567226.git.p.fedin@samsung.com> (raw)
Some hardware (like Raspberry Pi 2) is capable of running KVM, however lacks
functional vGIC registers. This series introduces software vGIC emulation for
such machines, allowing to fully use virtualization capabilities
Pavel Fedin (3):
KVM: arm: Add basic infrastructure for software vGIC emulation
KVM: arm: Introduce software emulation of vGICv2 CPU interface
KVM: arm: Enable vGICv2 software emulation
include/kvm/arm_vgic.h | 4 ++
virt/kvm/arm/vgic-v2-emul.c | 60 +++++++++++++++--
virt/kvm/arm/vgic-v2.c | 29 ++++----
virt/kvm/arm/vgic.c | 159 +++++++++++++++++++++++++++++++++-----------
virt/kvm/arm/vgic.h | 3 +
5 files changed, 196 insertions(+), 59 deletions(-)
--
2.1.4
next reply other threads:[~2015-06-29 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 9:53 Pavel Fedin [this message]
2015-06-29 9:53 ` [PATCH 1/3] KVM: arm: Add basic infrastructure for software vGIC emulation Pavel Fedin
2015-06-29 9:53 ` [PATCH 2/3] KVM: arm: Introduce software emulation of vGICv2 CPU interface Pavel Fedin
2015-06-29 9:53 ` [PATCH 3/3] KVM: arm: Enable vGICv2 software emulation Pavel Fedin
2015-06-29 12:17 ` Marc Zyngier
2015-06-29 12:37 ` Pavel Fedin
2015-06-29 12:48 ` Marc Zyngier
2015-06-29 12:13 ` [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation Marc Zyngier
2015-06-29 12:52 ` Christoffer Dall
2015-06-29 14:11 ` Andre Przywara
2015-06-29 14:15 ` Christoffer Dall
2015-06-29 15:29 ` Marc Zyngier
2015-06-30 8:16 ` Pavel Fedin
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=cover.1435567226.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.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 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.