[PULL,5/5] i386/kvm: add a comment explaining why .feat_names are commented out for Hyper-V feature bits

Commit Message

Eduardo Habkost Jan. 14, 2019, 2:34 p.m. UTC

From: Vitaly Kuznetsov <[e-mail]>

Hyper-V .feat_names are, unlike hardware features, commented out and it is
not obvious why we do that. Document the current status quo.

Signed-off-by: Vitaly Kuznetsov <[e-mail]>
Message-Id: <[e-mail]>
Signed-off-by: Eduardo Habkost <[e-mail]>
---
 target/i386/cpu.c | 7 +++++++
 1 file changed, 7 insertions(+)

Patch

diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 3ece83696e..2f5412592d 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -929,6 +929,13 @@  static FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
          */
         .no_autoenable_flags = ~0U,
     },
+    /*
+     * .feat_names are commented out for Hyper-V enlightenments because we
+     * don't want to have two different ways for enabling them on QEMU command
+     * line. Some features (e.g. "hyperv_time", "hyperv_vapic", ...) require
+     * enabling several feature bits simultaneously, exposing these bits
+     * individually may just confuse guests.
+     */
     [FEAT_HYPERV_EAX] = {
         .type = CPUID_FEATURE_WORD,
         .feat_names = {