From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Roman Kagan <rkagan@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/1] i386/kvm: TSC page clocksource for Hyper-V-on-KVM fixes
Date: Mon, 7 May 2018 18:57:58 +0200 [thread overview]
Message-ID: <2cb9716d-e5bf-7bd7-e217-8c2d090a2564@redhat.com> (raw)
In-Reply-To: <877eomtssk.fsf@vitty.brq.redhat.com>
On 02/05/2018 09:34, Vitaly Kuznetsov wrote:
> Vitaly Kuznetsov <vkuznets@redhat.com> writes:
>
>> Changes since v4:
>> - Rebase on top of Roman's patches.
>> - Drop PATCH2 as it is no longer needed (after adding explicit
>> hv_frequencies).
>>
>> 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 is enough.
>>
>> Enable Hyper-V reenlightenment MSRs to make things work.
>>
>
> Gentle ping :-)
>
> With Roman's Reviewed-by:, is there anything else needed from me to get
> this accepted?
>
> Thanks!
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-05-07 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 11:50 [Qemu-devel] [PATCH v5 0/1] i386/kvm: TSC page clocksource for Hyper-V-on-KVM fixes Vitaly Kuznetsov
2018-04-11 11:50 ` [Qemu-devel] [PATCH v5 1/1] i386/kvm: add support for Hyper-V reenlightenment MSRs Vitaly Kuznetsov
2018-04-11 12:01 ` Roman Kagan
2018-05-02 7:34 ` [Qemu-devel] [PATCH v5 0/1] i386/kvm: TSC page clocksource for Hyper-V-on-KVM fixes Vitaly Kuznetsov
2018-05-07 16:57 ` Paolo Bonzini [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=2cb9716d-e5bf-7bd7-e217-8c2d090a2564@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
--cc=vkuznets@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 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.