From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/4] Target CPU=Host implementation for KVM ARM/ARM64
Date: Wed, 02 Oct 2013 17:17:41 +0100 [thread overview]
Message-ID: <524C4725.3060700@arm.com> (raw)
In-Reply-To: <20131002160444.GA49034@lvm>
On 02/10/13 17:04, Christoffer Dall wrote:
> On Mon, Sep 30, 2013 at 02:20:04PM +0530, Anup Patel wrote:
>> It will be very useful for user space (QEMU/KVMTOOL) if it has a
>> method of querying VCPU target type matching to underlying Host.
>> We can use such querying mechanism and implement machine models
>> in user space where VCPU target type is always same-as/similar-to
>> underlying Host (i.e. Target CPU=Host).
>>
>> This patch series implements KVM_ARM_PREFERRED_TARGET vm ioclt for
>> querying VCPU target type matching underlying host. Using this new
>> ioctl we can implement VCPU target CPU=Host in user space.
>>
>> Also, it is not mandatory to call KVM_ARM_PREFERRED_TARGET vm ioctl
>> and the old method of trying all possible target types using the
>> KVM_ARM_VCPU_INIT ioctl to initialize VCPU works fine.
>>
> Looks good to me, as soon as Marc acks this one, I'll merge it.
Yup, go for it:
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2013-10-02 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 8:50 [PATCH v5 0/4] Target CPU=Host implementation for KVM ARM/ARM64 Anup Patel
2013-09-30 8:50 ` [PATCH v5 1/4] ARM: KVM: Implement kvm_vcpu_preferred_target() function Anup Patel
2013-09-30 8:50 ` [PATCH v5 2/4] ARM64: " Anup Patel
2013-09-30 8:50 ` [PATCH v5 3/4] ARM/ARM64: KVM: Implement KVM_ARM_PREFERRED_TARGET ioctl Anup Patel
2013-09-30 8:50 ` [PATCH v5 4/4] KVM: Add documentation for " Anup Patel
2013-10-02 16:04 ` [PATCH v5 0/4] Target CPU=Host implementation for KVM ARM/ARM64 Christoffer Dall
2013-10-02 16:17 ` Marc Zyngier [this message]
2013-10-02 18:32 ` 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=524C4725.3060700@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).