From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Roman Kagan <rkagan@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 4/8] i386/kvm: Implement 'hv-all' pass-through mode
Date: Tue, 29 Jan 2019 15:28:12 +0000 [thread overview]
Message-ID: <20190129152811.GF2650@work-vm> (raw)
In-Reply-To: <877eenze0u.fsf@vitty.brq.redhat.com>
* Vitaly Kuznetsov (vkuznets@redhat.com) wrote:
> "Dr. David Alan Gilbert" <dgilbert@redhat.com> writes:
>
> > I'm not sure what the equivalent bear traps are in the Hyper-V world,
> > but I'd be surprised if there weren't any; for example what happens
> > when someone upgrades one of their hosts to some minor version that
> > adds/removes a feature?
>
> Here we're talking about Hyper-V emulation in KVM, features only get
> added there, but even if it gets removed it will be detected by libvirt ...
OK, but then you do get the same behaviour; upgrade a host to a new
kernel/qemu and get a new enlightenment, and you can't back migrate to
the older one (possibly with no warning).
> >
> > Also, how does libvirt figure out that the features are actually the
> > same - does it need a bunch of detection code?
>
> ... as I *think* it compares Feature CPUID words (and all Hyper-V
> features which we enable with hv-all are there).
Not too bad if it does, but also look at the scary command lines we get
generated full of -cpu ...+feature,+feature,-feature,....
Dave
> --
> Vitaly
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-01-29 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 11:41 [Qemu-devel] [PATCH RFC 0/8] i386/kvm/hyper-v: refactor and implement 'hv-stimer-direct' and 'hv-all' enlightenments Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 1/8] Update linux headers (5.0-rc2) Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 2/8] i386/kvm: add support for KVM_GET_SUPPORTED_HV_CPUID Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 3/8] i386/kvm: move Hyper-V CPUID filling to hyperv_handle_properties() Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 4/8] i386/kvm: Implement 'hv-all' pass-through mode Vitaly Kuznetsov
2019-01-25 12:47 ` Roman Kagan
2019-01-25 13:46 ` Vitaly Kuznetsov
2019-01-28 11:30 ` Roman Kagan
2019-01-28 13:54 ` Vitaly Kuznetsov
2019-01-28 18:22 ` Dr. David Alan Gilbert
2019-01-28 19:10 ` Eduardo Habkost
2019-01-29 15:25 ` Vitaly Kuznetsov
2019-01-29 15:20 ` Vitaly Kuznetsov
2019-01-29 15:28 ` Dr. David Alan Gilbert [this message]
2019-01-29 15:43 ` Daniel P. Berrangé
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 5/8] i386/kvm: hv-evmcs requires hv-vapic Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 6/8] i386/kvm: hv-stimer requires hv-time and hv-synic Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 7/8] i386/kvm: hv-tlbflush/ipi require hv-vpindex Vitaly Kuznetsov
2019-01-25 11:41 ` [Qemu-devel] [PATCH RFC 8/8] i386/kvm: add support for Direct Mode for Hyper-V synthetic timers Vitaly Kuznetsov
2019-01-31 18:09 ` [Qemu-devel] [PATCH RFC 0/8] i386/kvm/hyper-v: refactor and implement 'hv-stimer-direct' and 'hv-all' enlightenments no-reply
2019-02-02 13:39 ` 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=20190129152811.GF2650@work-vm \
--to=dgilbert@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 \
--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).