From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 5/5] i386: provide simple 'hyperv=on' option to x86 machine types
Date: Tue, 05 Jan 2021 17:31:43 +0100 [thread overview]
Message-ID: <87a6tnibv4.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20210105170312.32cf0e12@redhat.com>
Igor Mammedov <imammedo@redhat.com> writes:
> On Tue, 05 Jan 2021 12:50:05 +0100
>
> I think there is a misunderstanding, idea was:
>
> cpu_initfn() {
> //current set
> cpu->default_hyperv_cpu_features = ACD
> }
>
> compat_props_5.1 {
> cpu.default_hyperv_cpu_features = AB
> }
>
> compat_props_5.2 {
> cpu.default_hyperv_cpu_features = ABC
> }
>
...
> I was talking about CPU features/properties only, it doesn't apply to other devices.
> It makes sense for machine to have a knob to create onboard hyperv specific
> devices if there is any (do we have any?).
>
> If there aren't any currently, I wouldn't bother with machine knob
> and just use -cpu foo,hv_default=on or -device cpu,hv_default=on
> like any other cpu feature.
>
We don't currently have any devices which are not 'CPU features' (in
QEMU terminology), however, we already have Vmbus and I can easily
imagine us implementing e.g. hartbeat/kvp/vss/... devices on top. We
*may* want to enable these 'automatically' and that's what make
'-machine' option preferable. It is, however, not a *must* right now and
we can indeed wait until these devices appear and be happy with
'hv_default' -cpu option for now. We will, however, need to teach upper
layers about the change when/if it happens.
--
Vitaly
next prev parent reply other threads:[~2021-01-05 16:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 10:32 [PATCH 0/5] i386: simplify Hyper-V enlightenments enablement Vitaly Kuznetsov
2020-11-19 10:32 ` [PATCH 1/5] i386: move hyperv_vendor_id initialization to x86_cpu_realizefn() Vitaly Kuznetsov
2021-03-10 11:27 ` Claudio Fontana
2021-03-10 11:43 ` Vitaly Kuznetsov
2021-03-10 12:18 ` Claudio Fontana
2021-03-10 13:13 ` Vitaly Kuznetsov
2020-11-19 10:32 ` [PATCH 2/5] i386: move hyperv_interface_id " Vitaly Kuznetsov
2020-11-19 10:32 ` [PATCH 3/5] i386: move hyperv_version_id " Vitaly Kuznetsov
2020-11-19 10:32 ` [PATCH 4/5] i386: move hyperv_limits " Vitaly Kuznetsov
2020-11-19 10:32 ` [PATCH 5/5] i386: provide simple 'hyperv=on' option to x86 machine types Vitaly Kuznetsov
2020-12-16 20:52 ` Eduardo Habkost
2020-12-17 9:34 ` Vitaly Kuznetsov
2020-12-18 17:13 ` Igor Mammedov
2020-12-18 18:07 ` Eduardo Habkost
2020-12-21 13:24 ` Igor Mammedov
2020-12-21 19:47 ` Eduardo Habkost
2020-12-21 20:39 ` David Hildenbrand
2021-01-04 12:54 ` Vitaly Kuznetsov
2021-01-04 18:29 ` Eduardo Habkost
2021-01-04 23:36 ` Igor Mammedov
2021-01-05 14:34 ` Eduardo Habkost
2021-01-05 15:10 ` Vitaly Kuznetsov
2021-01-05 16:33 ` Igor Mammedov
2021-01-05 16:31 ` Igor Mammedov
2021-01-05 17:02 ` Vitaly Kuznetsov
2021-01-05 18:19 ` Eduardo Habkost
2021-01-04 23:04 ` Igor Mammedov
2021-01-05 11:50 ` Vitaly Kuznetsov
2021-01-05 16:03 ` Igor Mammedov
2021-01-05 16:31 ` Vitaly Kuznetsov [this message]
2021-01-06 13:13 ` Igor Mammedov
2021-01-06 13:38 ` Vitaly Kuznetsov
2021-01-06 16:45 ` Igor Mammedov
2021-01-06 17:25 ` Eduardo Habkost
2021-01-07 9:14 ` Vitaly Kuznetsov
2021-01-06 17:02 ` Eduardo Habkost
2020-11-19 14:22 ` [PATCH 0/5] i386: simplify Hyper-V enlightenments enablement Claudio Fontana
2020-11-19 16:58 ` Vitaly Kuznetsov
2020-12-16 19:09 ` Eduardo Habkost
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=87a6tnibv4.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).