From: anup.patel@linaro.org (Anup Patel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] Target CPU=Host implementation for KVM ARM/ARM64
Date: Thu, 5 Sep 2013 20:15:59 +0530 [thread overview]
Message-ID: <1378392362-6773-1-git-send-email-anup.patel@linaro.org> (raw)
It will be very useful for user space if it has a method for specifying
KVM ARM/ARM64 to give a VCPU with target type suitable to underlying host
but with particular set of features.
In other words, user space might not be interested in having a particular
target type for VCPU but it will certainely want particular set of features
in the VCPU.
The patch tries to implement above described method of specifying VCPU
target CPU=Host from user space by extending the KVM_ARM_VCPU_INIT ioctl
and having a dummy target KVM_ARM_TARGET_HOST which means Target CPU
same as (or suitable to) underlying host.
This change in KVM_ARM_VCPU_INIT ioctl is backward compatible to its
current semantics hence does not break user space. The only difference
is that it will now update the struct kvm_vcpu_init instance (passed
by user space) with targer type and features of the VCPU that will be
emulated by KVM ARM/ARM64.
Anup Patel (3):
ARM: KVM: Implement target CPU=Host
ARM64: KVM: Implement target CPU=Host
KVM: ARM: Update documentation for KVM_ARM_VCPU_INIT ioctl
Documentation/virtual/kvm/api.txt | 5 ++++-
arch/arm/include/asm/kvm_host.h | 2 +-
arch/arm/include/uapi/asm/kvm.h | 1 +
arch/arm/kvm/arm.c | 9 ++++++++-
arch/arm/kvm/guest.c | 11 +++++++++--
arch/arm64/include/asm/kvm_host.h | 2 +-
arch/arm64/include/uapi/asm/kvm.h | 2 +-
arch/arm64/kvm/guest.c | 10 ++++++++--
8 files changed, 33 insertions(+), 9 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-09-05 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:45 Anup Patel [this message]
2013-09-05 14:46 ` [RFC PATCH 1/3] ARM: KVM: Implement target CPU=Host Anup Patel
2013-09-06 8:08 ` Claudio Fontana
2013-09-05 14:46 ` [RFC PATCH 2/3] ARM64: " Anup Patel
2013-09-06 8:09 ` Claudio Fontana
2013-09-05 14:46 ` [RFC PATCH 3/3] KVM: ARM: Update documentation for KVM_ARM_VCPU_INIT ioctl Anup Patel
2013-09-06 8:05 ` Claudio Fontana
2013-09-06 10:13 ` Anup Patel
2013-09-05 14:51 ` [RFC PATCH 0/3] Target CPU=Host implementation for KVM ARM/ARM64 Peter Maydell
2013-09-06 7:44 ` Anup Patel
2013-09-06 8:54 ` Alexander Graf
2013-09-06 9:06 ` Will Deacon
2013-09-06 10:09 ` Anup Patel
2013-09-06 10:49 ` Will Deacon
2013-09-06 10:51 ` Anup Patel
2013-09-06 10:52 ` Will Deacon
2013-09-06 10:05 ` Anup Patel
2013-09-06 10:24 ` Alexander Graf
2013-09-06 10:34 ` Marc Zyngier
2013-09-06 10:38 ` Anup Patel
2013-09-06 10:34 ` Anup Patel
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=1378392362-6773-1-git-send-email-anup.patel@linaro.org \
--to=anup.patel@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).