From: Pavel Fedin <p.fedin@samsung.com>
To: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH v5 0/2] KVM: arm/arm64: Allow to use KVM without in-kernel irqchip
Date: Mon, 30 Nov 2015 12:40:43 +0300 [thread overview]
Message-ID: <cover.1448874023.git.p.fedin@samsung.com> (raw)
This patch set brings back functionality which was broken in v4.0.
Unfortunately, currently it is impossible to take advantage of virtual
architected timer in this case, therefore guest, running in such
restricted mode, has to use some memory-mapped timer. But it is still
better than nothing.
Patch 0002 needs to be verified on PowerPC architecture, because i've
got an impression that KVM_CAP_IRQCHIP is forgotten there.
v4 => v5:
- Tested on top of kvmarm/next
- Dropped already applied part
- Fixed minor checkpatch issues
v3 => v4:
- Revert back to using switch on kvm_vgic_hyp_init() return code. I decided
to leave 'vgic_present = false' statement because it helps to understand
the code.
v2 => v3:
- Improved commit messages, added references to commits where the respective
functionality was broken
- Explicitly specify that the solution currently affects only vGIC and has
nothing to do with timer.
- Fixed code style according to previous notes
- Removed ARM64 save/restore patch introduced in v2 because it was already
obsolete for linux-next
- Modify KVM_CAP_IRQFD handling in correct place
v1 => v2:
- Do not use defensive approach in patch 0001. Use correct conditions in
callers instead
- Added ARM64-specific code, without which attempt to run a VM ends in a
HYP crash because of unset vGIC save/restore function pointers
Pavel Fedin (2):
arm/arm64: KVM: Detect vGIC presence at runtime
KVM: Make KVM_CAP_IRQFD dependent on KVM_CAP_IRQCHIP
arch/arm/kvm/arm.c | 22 ++++++++++++++++++++--
virt/kvm/kvm_main.c | 6 ++++--
2 files changed, 24 insertions(+), 4 deletions(-)
--
2.4.4
next reply other threads:[~2015-11-30 9:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 9:40 Pavel Fedin [this message]
2015-11-30 9:40 ` [PATCH v5 1/2] arm/arm64: KVM: Detect vGIC presence at runtime Pavel Fedin
2016-04-21 21:41 ` Alexander Graf
2016-04-21 22:04 ` Peter Maydell
2016-04-21 22:35 ` Alexander Graf
2016-04-21 22:41 ` Peter Maydell
2016-04-22 7:50 ` Marc Zyngier
2015-11-30 9:40 ` [PATCH v5 2/2] KVM: Make KVM_CAP_IRQFD dependent on KVM_CAP_IRQCHIP Pavel Fedin
2015-11-30 11:26 ` Cornelia Huck
2015-11-30 11:56 ` Pavel Fedin
2015-11-30 12:13 ` Cornelia Huck
2015-11-30 12:41 ` Pavel Fedin
2015-11-30 14:38 ` Cornelia Huck
2015-11-30 14:45 ` Pavel Fedin
2015-12-01 11:07 ` Pavel Fedin
2015-12-01 16:00 ` Paolo Bonzini
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.1448874023.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.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).