| commit | 864867b91b48d38e2bfc7b225197901e6f7d8216 | |
| author | Eduardo Habkost <ehabkost@redhat.com> | |
| Fri, 3 Oct 2014 19:39:48 +0000 (3 16:39 -0300) | ||
| committer | Andreas Färber <afaerber@suse.de> | |
| Tue, 4 Nov 2014 14:35:47 +0000 (4 15:35 +0100) | ||
| tree | 0a50bc8d7cc9863b214849b72466682a96d6ae55 | treesnapshot (tar.gz zip) |
| parent | 1cadaa9482244f7d6477afc34c04a5dad84afdde | commitdiff |
target-i386: Disable CPUID_ACPI by default in KVM mode
KVM never supported the CPUID_ACPI flag, so it doesn't make sense to
have it enabled by default when KVM is enabled.
The motivation here is exactly the same we had for the MONITOR flag
(disabled by commit 136a7e9a85d7047461f8153f7d12c514a3d68f69).
And like in the MONITOR flag case, we don't need machine-type compat code
because it is currently impossible to run a KVM VM with the ACPI flag set.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
KVM never supported the CPUID_ACPI flag, so it doesn't make sense to
have it enabled by default when KVM is enabled.
The motivation here is exactly the same we had for the MONITOR flag
(disabled by commit 136a7e9a85d7047461f8153f7d12c514a3d68f69).
And like in the MONITOR flag case, we don't need machine-type compat code
because it is currently impossible to run a KVM VM with the ACPI flag set.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
| target-i386/cpu.c | diffblobblamehistory |