From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>
Subject: [Qemu-devel] [PATCH v3 0/2] i386/kvm: TSC page clocksource for Hyper-V-on-KVM fixes
Date: Tue, 20 Mar 2018 18:34:58 +0100 [thread overview]
Message-ID: <20180320173500.32065-1-vkuznets@redhat.com> (raw)
Changes since v2:
- add hv-reenlightenment CPU property [Roman Kagan, Paolo Bonzini]
- add a comment to feature_word_info [Roman Kagan]
Previously, Ladi was working on enabling TSC page clocksource for nested
Hyper-V-on-KVM workloads. He found out that if Hyper-V frequency MSRs are
exposed to L1 as well as INVTSC flag Hyper-V enables TSC page clocksource
to its guests. Qemu doesn't pass INVTSC by default as it is a migration
blocker.
I found out there's a different way to make Hyper-V like us: expose
Reenlightenment MSRs to it. KVM doesn't fully support the feature as
we're still unable to migrate nested environments but rudimentary support
we have there (kvm/queue only currently) is enough.
Enable Hyper-V reenlightenment MSRs and expose frequency MSRs even without
INVTSC to make things work.
Vitaly Kuznetsov (2):
i386/kvm: add support for Hyper-V reenlightenment MSRs
i386/kvm: lower requirements for Hyper-V frequency MSRs exposure
target/i386/cpu.c | 4 +++-
target/i386/cpu.h | 4 ++++
target/i386/hyperv-proto.h | 9 ++++++++-
target/i386/kvm.c | 41 +++++++++++++++++++++++++++++++++++++++--
target/i386/machine.c | 24 ++++++++++++++++++++++++
5 files changed, 78 insertions(+), 4 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-20 17:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:34 Vitaly Kuznetsov [this message]
2018-03-20 17:34 ` [Qemu-devel] [PATCH v3 1/2] i386/kvm: add support for Hyper-V reenlightenment MSRs Vitaly Kuznetsov
2018-03-20 18:32 ` Eduardo Habkost
2018-03-21 11:09 ` Roman Kagan
2018-03-21 13:09 ` Roman Kagan
2018-03-21 11:24 ` Roman Kagan
2018-03-22 17:09 ` Marcelo Tosatti
2018-03-22 17:39 ` Vitaly Kuznetsov
2018-03-20 17:35 ` [Qemu-devel] [PATCH v3 2/2] i386/kvm: lower requirements for Hyper-V frequency MSRs exposure Vitaly Kuznetsov
2018-03-21 12:10 ` Roman Kagan
2018-03-21 13:18 ` Vitaly Kuznetsov
2018-03-21 16:57 ` Roman Kagan
2018-03-21 20:19 ` Eduardo Habkost
2018-03-22 13:00 ` Roman Kagan
2018-03-22 13:22 ` Eduardo Habkost
2018-03-22 13:58 ` Roman Kagan
2018-03-22 18:38 ` Eduardo Habkost
2018-03-23 9:45 ` Roman Kagan
2018-03-23 19:48 ` Eduardo Habkost
2018-03-26 14:20 ` Roman Kagan
2018-03-21 15:33 ` Paolo Bonzini
2018-03-21 16:17 ` Vitaly Kuznetsov
2018-03-21 17:17 ` Roman Kagan
2018-03-21 20:06 ` Eduardo Habkost
2018-03-21 16:47 ` Roman Kagan
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=20180320173500.32065-1-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
/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).