From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.12 v3 0/2] i386/hyperv: fully control Hyper-V features in CPUID
Date: Thu, 5 Apr 2018 17:52:00 +0200 [thread overview]
Message-ID: <84d1f39e-856b-5f5c-0352-37554b825f55@redhat.com> (raw)
In-Reply-To: <20180330170209.20627-1-rkagan@virtuozzo.com>
On 30/03/2018 19:02, Roman Kagan wrote:
> In order to guarantee compatibility on migration, QEMU should have
> complete control over the features it announces to the guest via CPUID.
>
> However, a number of Hyper-V-related features happen to depend on the
> support in the underlying KVM, with no regard to QEMU configuration.
>
> Make QEMU regain control over what Hyper-V features it announces to the
> guest.
>
> Note #1: the patches are also being proposed[*] for stable-2.11, even
> though one of them introduces a new cpu property. This is done to
> minimize the number of published QEMU releases where the behavior of the
> features is unpredictable, with potentially fatal consequences for the
> guest.
>
> Note #2: there are other problems in the surrounding code, like ugly
> error reporting or inconsistent population of MSRs. I think this can be
> put off to post-2.12.
>
> [*] for the stable branch the second patch will have error returns
> replaced with warnings; I'll post a separate series.
>
> v2 -> v3:
> - include the fix for 'hv-time' missed previously
>
> v1 -> v2:
> - indicate what flag requested the feature that can't be enabled in the
> error message
> - fix a typo in the error message for VP_RUNTIME
Queued, thanks.
Paolo
>
> Roman Kagan (2):
> i386/hyperv: add hv-frequencies cpu property
> i386/hyperv: error out if features requested but unsupported
>
> target/i386/cpu.h | 1 +
> target/i386/cpu.c | 1 +
> target/i386/kvm.c | 56 ++++++++++++++++++++++++++++++++++++++++++-------------
> 3 files changed, 45 insertions(+), 13 deletions(-)
>
prev parent reply other threads:[~2018-04-05 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 17:02 [Qemu-devel] [PATCH for-2.12 v3 0/2] i386/hyperv: fully control Hyper-V features in CPUID Roman Kagan
2018-03-30 17:02 ` [Qemu-devel] [PATCH for-2.12 v3 1/2] i386/hyperv: add hv-frequencies cpu property Roman Kagan
2018-03-30 17:02 ` [Qemu-devel] [PATCH for-2.12 v3 2/2] i386/hyperv: error out if features requested but unsupported Roman Kagan
2018-03-30 19:40 ` Eduardo Habkost
2018-03-31 8:33 ` [Qemu-devel] [PATCH for-2.12 v3 0/2] i386/hyperv: fully control Hyper-V features in CPUID no-reply
2018-03-31 9:00 ` no-reply
2018-04-05 15:52 ` 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=84d1f39e-856b-5f5c-0352-37554b825f55@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--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).