From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, dmatlack@google.com
Subject: Re: [PATCH 0/2] KVM: nVMX: expose VMX capabilities as MSR features
Date: Wed, 7 Mar 2018 16:55:49 +0100 [thread overview]
Message-ID: <20180307155549.GD12290@flask> (raw)
In-Reply-To: <1519648809-16694-1-git-send-email-pbonzini@redhat.com>
2018-02-26 13:40+0100, Paolo Bonzini:
> These patches add the VMX capability MSRs to the /dev/kvm ioctls
> KVM_GET_MSR_FEATURE_INDEX_LIST and KVM_GET_MSRS, so that userspace
> can easily probe which VMX features are actually supported by KVM.
>
> This will help the implementation of nested hypervisor migration,
> even for heterogeneous clusters.
>
> Patch 1 is just refactoring, while patch 2 implements the feature.
Queued, thanks.
prev parent reply other threads:[~2018-03-07 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 12:40 [PATCH 0/2] KVM: nVMX: expose VMX capabilities as MSR features Paolo Bonzini
2018-02-26 12:40 ` [PATCH 1/2] KVM: nVMX: introduce struct nested_vmx_msrs Paolo Bonzini
2018-02-26 12:40 ` [PATCH 2/2] KVM: nVMX: expose VMX capabilities for nested hypervisors to userspace Paolo Bonzini
2018-03-07 15:55 ` Radim Krčmář [this message]
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=20180307155549.GD12290@flask \
--to=rkrcmar@redhat.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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