| commit | 31085338293a1203187c6ef6dba9dfce14021189 | |
| author | Thomas Huth <thuth@redhat.com> | |
| Mon, 28 May 2018 18:11:19 +0000 (28 20:11 +0200) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Mon, 11 Jun 2018 23:33:52 +0000 (12 09:33 +1000) | ||
| tree | d22938b7cd3fcb91aedc3f0948d14b5e2afed935 | treesnapshot (tar.gz zip) |
| parent | e20c63140a185c166e91d8c68a2aa6bb99e600c3 | commitdiff |
target/ppc: Use proper logging function for possible guest errors
fprintf() and qemu_log_separate() are frowned upon these days for printing
logging information in QEMU. Accessing the wrong SPRs indicates wrong guest
behaviour in most cases, and we've got a proper way to log such situations,
which is the qemu_log_mask(LOG_GUEST_ERROR, ...) function. So use this
function now for logging the bad SPR accesses instead.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
fprintf() and qemu_log_separate() are frowned upon these days for printing
logging information in QEMU. Accessing the wrong SPRs indicates wrong guest
behaviour in most cases, and we've got a proper way to log such situations,
which is the qemu_log_mask(LOG_GUEST_ERROR, ...) function. So use this
function now for logging the bad SPR accesses instead.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
| target/ppc/translate.c | diffblobblamehistory |