From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: KVM: allow VMs with more than 4 CPUs
Date: Fri, 18 Oct 2013 18:19:02 +0100 [thread overview]
Message-ID: <1382116746-8757-1-git-send-email-marc.zyngier@arm.com> (raw)
Currently, KVM/ARM is limited to 4 A7 or A15 per VM. This is due to
the fact that KVM doesn't know about clusters, and puts all CPUs at
affinity level 0.
This patch series removes this limitation by allowing additionnal CPUs
to be part of a separate cluster (affinity level 1).
This also requires a patch to kvmtool so the generated DT matches the
expectations of the guest (posted separately).
Tested on TC2 and arm64 model.
Patches based on Christoffer's next tree as of today.
Marc Zyngier (4):
arm/arm64: KVM: PSCI: use MPIDR to identify a target CPU
ARM: KVM: Fix MPIDR computing to support virtual clusters
ARM: KVM: fix L2CTLR to be per-cluster
ARM: KVM: drop limitation to 4 CPU VMs
arch/arm/include/asm/kvm_emulate.h | 5 +++++
arch/arm/kvm/coproc.c | 14 ++++++++++----
arch/arm/kvm/psci.c | 17 +++++++++++++----
arch/arm/kvm/reset.c | 4 ----
arch/arm64/include/asm/kvm_emulate.h | 5 +++++
5 files changed, 33 insertions(+), 12 deletions(-)
--
1.8.2.3
next reply other threads:[~2013-10-18 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 17:19 Marc Zyngier [this message]
2013-10-18 17:19 ` [PATCH 1/4] arm/arm64: KVM: PSCI: use MPIDR to identify a target CPU Marc Zyngier
2013-10-18 17:19 ` [PATCH 2/4] ARM: KVM: Fix MPIDR computing to support virtual clusters Marc Zyngier
2013-10-18 17:19 ` [PATCH 3/4] ARM: KVM: fix L2CTLR to be per-cluster Marc Zyngier
2013-10-18 17:19 ` [PATCH 4/4] ARM: KVM: drop limitation to 4 CPU VMs Marc Zyngier
2013-10-22 14:10 ` [PATCH 0/4] ARM: KVM: allow VMs with more than 4 CPUs 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=1382116746-8757-1-git-send-email-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--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).