From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Makarand Sonare <makarandsonare@google.com>, kvm <kvm@vger.kernel.org>
Subject: Re: KVM patches for Hyper-V improvements
Date: Fri, 03 Dec 2021 09:09:09 +0100 [thread overview]
Message-ID: <87r1au6rfe.fsf@redhat.com> (raw)
In-Reply-To: <CA+qz5sqUKk46BcRKCyM1rdvtGL3QE7C8gDt0D7qx8_x_M8bKtQ@mail.gmail.com>
Makarand Sonare <makarandsonare@google.com> writes:
> Hello Vitaly,
> I am interested in knowing the exact set of KVM
> patches that were added for the Nested Hyper-V scenario. Could you
> please point me to them?
Hi Makarand,
are you interested in patches since some upstream kernel version or
since the beginning of time? Thing is, some Hyper-V enlightenments
benefit both Windows and Hyper-V and some are specific to Hyper-V. Out
of top of my head, 'direct synthetic timers', 'Enlightened VMCS', and
'Enlightened MSR-Bitmap' features are Hyper-V specific. Patch list is
pretty long, see for example
$ git log --author vkuznets@redhat.com --oneline -i --grep 'enlightened.*vmcs' arch/x86/kvm/
and
$ git log --author vkuznets@redhat.com --oneline -i --grep 'direct.*syn' arch/x86/kvm/
Enlightened MSR-Bitmap is only in kvm/master:
ceef7d10dfb6 KVM: x86: VMX: hyper-v: Enlightened MSR-Bitmap support
The list is likely incomplete as there are pre-requisites for these
patches which may not have the required keywords. There were fixes in
other parts of KVM for nested Hyper-V as well but I don't know an easy
way to find them (grepping for 'Hyper-V/hyperv' in the log would be a
good start but we'll certainly miss something).
Please let me know if that's what you're looking for and I'll try to
give you more precise information.
--
Vitaly
next prev parent reply other threads:[~2021-12-03 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 1:32 KVM patches for Hyper-V improvements Makarand Sonare
2021-12-03 8:09 ` Vitaly Kuznetsov [this message]
2021-12-03 18:38 ` Makarand Sonare
2021-12-06 9:52 ` Vitaly Kuznetsov
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=87r1au6rfe.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=makarandsonare@google.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