qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@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: Re: [Qemu-devel] [PATCH v3 2/2] i386/kvm: lower requirements for Hyper-V frequency MSRs exposure
Date: Wed, 21 Mar 2018 16:33:33 +0100	[thread overview]
Message-ID: <46c08ea1-27f7-e581-f93f-cf635950062f@redhat.com> (raw)
In-Reply-To: <20180320173500.32065-3-vkuznets@redhat.com>

On 20/03/2018 18:35, Vitaly Kuznetsov wrote:
> +        if (has_msr_hv_frequencies && env->tsc_khz) {
>              env->features[FEAT_HYPERV_EAX] |= HV_ACCESS_FREQUENCY_MSRS;
>              env->features[FEAT_HYPERV_EDX] |= HV_FREQUENCY_MSRS_AVAILABLE;
>          }

Since you have added cpu->hyperv_reenlightenment, I'd rather change this
so that we don't make the "license to change guest ABI across migration"
apply more.  We can exploit the fact that Windows doesn't even use the
MSRs unless either invtsc or re-enlightenment is present.  Something
like this:

       if (has_msr_hv_frequencies && env->tsc_khz &&
	   (tsc_is_stable_and_known(env) ||
            cpu->hyperv_reenlightenment))

will make the MSRs visible in all useful cases, without having to add
yet another knob.

(Don't worry, this backwards-compatibility stuff is the hardest part.
I'm so happy that Eduardo is the one maintaining it :)).

Paolo

  parent reply	other threads:[~2018-03-21 15:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 17:34 [Qemu-devel] [PATCH v3 0/2] i386/kvm: TSC page clocksource for Hyper-V-on-KVM fixes Vitaly Kuznetsov
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 [this message]
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=46c08ea1-27f7-e581-f93f-cf635950062f@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 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).