diff options
| author | Laurent Vivier | 2017-04-14 10:37:15 +0200 |
|---|---|---|
| committer | Markus Armbruster | 2017-04-21 07:18:23 +0200 |
| commit | 40fda982f2e887f7d5cc36b8a7e3b5a07a1e6704 (patch) | |
| tree | d80c622982d48ff5d94015409181d432ac691c8c /include | |
| parent | arm: remove remaining cannot_destroy_with_object_finalize_yet (diff) | |
| download | qemu-40fda982f2e887f7d5cc36b8a7e3b5a07a1e6704.tar.gz qemu-40fda982f2e887f7d5cc36b8a7e3b5a07a1e6704.tar.xz qemu-40fda982f2e887f7d5cc36b8a7e3b5a07a1e6704.zip | |
ppc: remove cannot_destroy_with_object_finalize_yet
This removes the assert(kvm_enabled()) from kvmppc_host_cpu_initfn()
This assert can never be triggered as the function is only registered
when KVM is available (see also 4c315c2
"qdev: Protect device-list-properties against broken devices").
So we can remove the cannot_destroy_with_object_finalize_yet from
kvmppc_host_cpu_class_init() without fear and beyond reproach.
(as it has already be done for i386 with 771a13e "i386: Unset
cannot_destroy_with_object_finalize_yet on "host" model" and
e435601 "target-i386: Remove assert(kvm_enabled()) from
host_x86_cpu_initfn()")
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Message-Id: <20170414083717.13641-3-lvivier@redhat.com>
Acked-by: Peter Maydell <peter.maydell@linaro.org>
Acked-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions