From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: kvmarm@lists.cs.columbia.edu, "Andreas Färber" <afaerber@suse.de>,
patches@linaro.org
Subject: [Qemu-devel] [RFC 0/2] target-arm: Provide '-cpu host' when running KVM
Date: Tue, 13 Aug 2013 19:03:01 +0100 [thread overview]
Message-ID: <1376416983-30838-1-git-send-email-peter.maydell@linaro.org> (raw)
These patches add support to target-arm for '-cpu host'.
The general semantics are the same as for ppc and x86 (ie "whatever
the host kernel can support that looks basically like the host
CPU"), but the mechanism is a little different.
The kernel API (currently still proposed rather than implemented,
hence the RFC nature of this patchset) is that the existing
KVM_ARM_VCPU_INIT supports a new 'target' value KVM_ARM_TARGET_HOST,
which it treats as "whatever you are". On the userspace side,
we use this if the kernel supports it. If it doesn't then we
know the kernel must be an A15-on-A15 only one, and so can
safely implement '-cpu host' with KVM_ARM_TARGET_CORTEX_A15.
In order to find out details of the vCPU so we can correctly
set up our ARMCPU objects, we create a scratch VM and a single
cpu within it; we can then use the existing "read registers"
API to access the ID registers. We do this once at startup
when we register the new QOM type.
('-cpu host' is also going to be useful for AArch64 because
it gives us a path to providing KVM support without having
to implement a model of a specific v8 CPU and all its system
registers...)
Peter Maydell (2):
target-arm: Don't hardcode KVM target CPU to be A15
target-arm: Provide '-cpu host' when running KVM
target-arm/helper.c | 6 ++
target-arm/kvm.c | 227 ++++++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 231 insertions(+), 2 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-08-13 18:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:03 Peter Maydell [this message]
2013-08-13 18:03 ` [Qemu-devel] [RFC 1/2] target-arm: Don't hardcode KVM target CPU to be A15 Peter Maydell
2013-08-13 18:03 ` [Qemu-devel] [RFC 2/2] target-arm: Provide '-cpu host' when running KVM Peter Maydell
2013-08-14 6:32 ` [Qemu-devel] [RFC 0/2] " Alexander Graf
2013-08-14 8:11 ` Marc Zyngier
2013-08-14 8:16 ` Alexander Graf
2013-08-14 8:27 ` Marc Zyngier
2013-08-14 8:46 ` Alexander Graf
2013-08-14 9:07 ` Peter Maydell
2013-08-14 9:11 ` Alexander Graf
2013-08-14 9:23 ` Peter Maydell
2013-08-14 9:30 ` Alexander Graf
2013-08-14 17:26 ` Christoffer Dall
2013-08-14 17:31 ` Alexander Graf
2013-08-14 17:39 ` Christoffer Dall
2013-08-14 17:44 ` Alexander Graf
2013-08-14 18:18 ` Christoffer Dall
2013-08-14 18:21 ` Alexander Graf
2013-08-14 18:27 ` Peter Maydell
2013-08-14 19:23 ` Alexander Graf
2013-08-14 18:28 ` Christoffer Dall
2013-08-14 19:28 ` Alexander Graf
2013-08-14 20:33 ` Christoffer Dall
2013-08-14 20:47 ` Alexander Graf
2013-08-14 20:56 ` Christoffer Dall
2013-08-14 21:00 ` Alexander Graf
2013-08-25 14:42 ` Gleb Natapov
2013-08-25 15:11 ` Peter Maydell
2013-08-26 11:18 ` Gleb Natapov
2013-08-26 12:17 ` Peter Maydell
2013-08-14 18:11 ` Peter Maydell
2013-08-14 18:15 ` Alexander Graf
2013-08-14 18:24 ` Peter Maydell
2013-08-14 9:06 ` Peter Maydell
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=1376416983-30838-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.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).