diff options
| author | Greg Kurz | 2018-07-02 18:56:06 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2018-07-06 18:39:19 +0200 |
| commit | 02693cc4f4aacf82cb73559dfa9af76ce4b13d11 (patch) | |
| tree | a84675ee01579284a8bb24d063853f84806e371c /scripts/qapi/__init__.py | |
| parent | qtest: Use cpu address space instead of system memory (diff) | |
| download | qemu-02693cc4f4aacf82cb73559dfa9af76ce4b13d11.tar.gz qemu-02693cc4f4aacf82cb73559dfa9af76ce4b13d11.tar.xz qemu-02693cc4f4aacf82cb73559dfa9af76ce4b13d11.zip | |
i386: fix '-cpu ?' output for host cpu type
Since commit d6dcc5583e7, '-cpu ?' shows the description of the
X86_CPU_TYPE_NAME("max") for the host CPU model:
Enables all features supported by the accelerator in the current host
instead of the expected:
KVM processor with all supported host features
or
HVF processor with all supported host features
This is caused by the early use of kvm_enabled() and hvf_enabled() in
a class_init function. Since the accelerator isn't configured yet, both
helpers return false unconditionally.
A QEMU binary will only be compiled with one of these accelerators, not
both. The appropriate description can thus be decided at build time.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <153055056654.212317.4697363278304826913.stgit@bahia.lan>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/qapi/__init__.py')
0 files changed, 0 insertions, 0 deletions