| commit | 4482e05cbbb7e50e476f6a9500cf0b38913bd939 | |
| author | Igor Mammedov <imammedo@redhat.com> | |
| Wed, 13 Sep 2017 16:04:54 +0000 (13 18:04 +0200) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Tue, 19 Sep 2017 12:09:32 +0000 (19 09:09 -0300) | ||
| tree | c2135cfd57c8f7fe0c50ddf19e43e98479383c08 | treesnapshot (tar.gz zip) |
| parent | 3c72234c98004a01d79a24f78b07053cfebd0f22 | commitdiff |
cpu: make cpu_generic_init() abort QEMU on error
Almost every user of cpu_generic_init() checks for
returned NULL and then reports failure in a custom way
and aborts process.
Some users assume that call can't fail and don't check
for failure, though they should have checked for it.
In either cases cpu_generic_init() failure is fatal,
so instead of checking for failure and reporting
it various ways, make cpu_generic_init() report
errors in consistent way and terminate QEMU on failure.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <1505318697-77161-3-git-send-email-imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Almost every user of cpu_generic_init() checks for
returned NULL and then reports failure in a custom way
and aborts process.
Some users assume that call can't fail and don't check
for failure, though they should have checked for it.
In either cases cpu_generic_init() failure is fatal,
so instead of checking for failure and reporting
it various ways, make cpu_generic_init() report
errors in consistent way and terminate QEMU on failure.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <1505318697-77161-3-git-send-email-imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
38 files changed: