diff options
author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2021-04-22 18:11:18 +0200 |
---|---|---|
committer | Eduardo Habkost <ehabkost@redhat.com> | 2021-05-31 15:53:03 -0400 |
commit | 061817a7ccd9e1c028153f308c541c299a009ef8 (patch) | |
tree | 7f254e57df217a0e67aad7049f213ad124f344fd /qemu-io.c | |
parent | e1a66a1e27eee8b025954713d28b9e74d95a5271 (diff) | |
download | qemu-061817a7ccd9e1c028153f308c541c299a009ef8.zip qemu-061817a7ccd9e1c028153f308c541c299a009ef8.tar.gz qemu-061817a7ccd9e1c028153f308c541c299a009ef8.tar.bz2 |
i386: drop FEAT_HYPERV feature leaves
Hyper-V feature leaves are weird. We have some of them in
feature_word_info[] array but we don't use feature_word_info
magic to enable them. Neither do we use feature_dependencies[]
mechanism to validate the configuration as it doesn't allign
well with Hyper-V's many-to-many dependency chains. Some of
the feature leaves hold not only feature bits, but also values.
E.g. FEAT_HV_NESTED_EAX contains both features and the supported
Enlightened VMCS range.
Hyper-V features are already represented in 'struct X86CPU' with
uint64_t hyperv_features so duplicating them in env->features adds
little (or zero) benefits. THe other half of Hyper-V emulation features
is also stored with values in hyperv_vendor_id[], hyperv_limits[],...
so env->features[] is already incomplete.
Remove Hyper-V feature leaves from env->features[] completely.
kvm_hyperv_properties[] is converted to using raw CPUID func/reg
pairs for features, this allows us to get rid of hv_cpuid_get_fw()
conversion.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20210422161130.652779-8-vkuznets@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'qemu-io.c')
0 files changed, 0 insertions, 0 deletions