mirror of
https://github.com/yuzu-emu/unicorn.git
synced 2025-02-02 05:01:06 +00:00
i386/kvm: add a comment explaining why .feat_names are commented out for Hyper-V feature bits
Hyper-V .feat_names are, unlike hardware features, commented out and it is not obvious why we do that. Document the current status quo. Backports commit abd5fc4c862d033a989552914149f01c9476bb16 from qemu
This commit is contained in:
parent
2873612479
commit
b6cc2c4e06
|
@ -1025,6 +1025,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,
|
||||
|
|
Loading…
Reference in a new issue