From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 0/2] i386: Add support for Hyper-V Enlightened MSR-Bitmap feature
Date: Thu, 27 Jan 2022 10:45:01 +0100 [thread overview]
Message-ID: <87bkzxh5r6.fsf@redhat.com> (raw)
In-Reply-To: <20220105085704.1267530-1-vkuznets@redhat.com>
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> The new nested specific enlightenment speeds up L2 vmexits by avoiding
> unnecessary updates to L2 MSR-Bitmap. Support for both VMX and SVM is
> coming to KVM:
> https://lore.kernel.org/kvm/20211129094704.326635-1-vkuznets@redhat.com/
> https://lore.kernel.org/kvm/20211220152139.418372-1-vkuznets@redhat.com/
>
Ping)
VMX part made it to KVM in v5.17-rc1:
commit 502d2bf5f2fd7c05adc2d4f057910bd5d4c4c63e
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date: Mon Nov 29 10:47:04 2021 +0100
KVM: nVMX: Implement Enlightened MSR Bitmap feature
SVM part is still pending, will likely go to 5.18. QEMU enablement code
is, however, the same.
> Vitaly Kuznetsov (2):
> i386: Use hv_build_cpuid_leaf() for HV_CPUID_NESTED_FEATURES
> i386: Hyper-V Enlightened MSR bitmap feature
>
> docs/hyperv.txt | 10 ++++++++++
> target/i386/cpu.c | 2 ++
> target/i386/cpu.h | 2 +-
> target/i386/kvm/hyperv-proto.h | 5 +++++
> target/i386/kvm/kvm.c | 30 ++++++++++++++++++++++--------
> 5 files changed, 40 insertions(+), 9 deletions(-)
--
Vitaly
prev parent reply other threads:[~2022-01-27 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 8:57 [PATCH 0/2] i386: Add support for Hyper-V Enlightened MSR-Bitmap feature Vitaly Kuznetsov
2022-01-05 8:57 ` [PATCH 1/2] i386: Use hv_build_cpuid_leaf() for HV_CPUID_NESTED_FEATURES Vitaly Kuznetsov
2022-01-05 8:57 ` [PATCH 2/2] i386: Hyper-V Enlightened MSR bitmap feature Vitaly Kuznetsov
2022-01-27 9:45 ` Vitaly Kuznetsov [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=87bkzxh5r6.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.