aboutsummaryrefslogtreecommitdiff
path: root/target-unicore32/ucf64_helper.c
diff options
context:
space:
mode:
authorEduardo Habkost <ehabkost@redhat.com>2013-01-04 20:01:04 -0200
committerAndreas Färber <afaerber@suse.de>2013-01-08 21:03:44 +0100
commitfcb93c036053ca8a5cfc02ca72b1b80dd2062423 (patch)
tree1d3e725e9e0b03180e94f9695196a62add109e78 /target-unicore32/ucf64_helper.c
parent961f839570f01d60a0b224248e6e56fc1d675793 (diff)
target-i386: kvm: -cpu host: Use GET_SUPPORTED_CPUID for SVM features
The existing -cpu host code simply sets every bit inside svm_features (initializing it to -1), and that makes it impossible to make the enforce/check options work properly when the user asks for SVM features explicitly in the command-line. So, instead of initializing svm_features to -1, use GET_SUPPORTED_CPUID to fill only the bits that are supported by the host (just like we do for all other CPUID feature words inside kvm_cpu_fill_host()). This will keep the existing behavior (as filter_features_for_kvm() already uses GET_SUPPORTED_CPUID to filter svm_features), but will allow us to properly check for KVM features inside kvm_check_features_against_host() later. For example, we will be able to make this: $ qemu-system-x86_64 -cpu ...,+pfthreshold,enforce refuse to start if the SVM "pfthreshold" feature is not supported by the host (after we fix kvm_check_features_against_host() to check SVM flags as well). Signed-off-by: Eduardo Habkost <ehabkost@redhat.com> Reviewed-by: Gleb Natapov <gleb@redhat.com> Signed-off-by: Andreas Färber <afaerber@suse.de>
Diffstat (limited to 'target-unicore32/ucf64_helper.c')
0 files changed, 0 insertions, 0 deletions