| commit | 0d914f39a77954bf5472b16130aeefe573a068f5 | |
| author | Eduardo Habkost <ehabkost@redhat.com> | |
| Tue, 10 Apr 2018 21:15:34 +0000 (10 18:15 -0300) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Mon, 16 Apr 2018 16:36:52 +0000 (16 13:36 -0300) | ||
| tree | bfbf4fcda57e91c664889f294ad31816112d7ef1 | treesnapshot (tar.gz zip) |
| parent | 042f6a31af3d38eefc6ec995cce1d762c41d4515 | commitdiff |
i386: Don't automatically enable FEAT_KVM_HINTS bits
The assumption in the cpu->max_features code is that anything
enabled on GET_SUPPORTED_CPUID should be enabled on "-cpu host".
This shouldn't be the case for FEAT_KVM_HINTS.
This adds a new FeatureWordInfo::no_autoenable_flags field, that
can be used to prevent FEAT_KVM_HINTS bits to be enabled
automatically.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20180410211534.26079-1-ehabkost@redhat.com>
Tested-by: Wanpeng Li <wanpengli@tencent.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
The assumption in the cpu->max_features code is that anything
enabled on GET_SUPPORTED_CPUID should be enabled on "-cpu host".
This shouldn't be the case for FEAT_KVM_HINTS.
This adds a new FeatureWordInfo::no_autoenable_flags field, that
can be used to prevent FEAT_KVM_HINTS bits to be enabled
automatically.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20180410211534.26079-1-ehabkost@redhat.com>
Tested-by: Wanpeng Li <wanpengli@tencent.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| target/i386/cpu.c | diffblobblamehistory |