diff options
| author | Mark Cave-Ayland <[email protected]> | 2019-06-14 19:57:45 +0100 |
|---|---|---|
| committer | Paul Mackerras <[email protected]> | 2019-06-17 16:20:43 +1000 |
| commit | 3bda7f0ae0f786b202c0c5124c208be067acca30 (patch) | |
| tree | 9bbb1f8bb25bbdeb1820a82c0cf7afc0cc8cc1ea /scripts/gdb/linux/modules.py | |
| parent | 0e84ec96b561d298bc9a22d58e7a4730bc408aca (diff) | |
KVM: PPC: Book3S PR: Fix software breakpoints
QEMU's kvm_handle_debug() function identifies software breakpoints by checking
for a value of 0 in kvm_debug_exit_arch's status field. Since this field isn't
explicitly set to 0 when the software breakpoint instruction is detected, any
previous non-zero value present causes a hang in QEMU as it tries to process
the breakpoint instruction incorrectly as a hardware breakpoint.
Ensure that the kvm_debug_exit_arch status field is set to 0 when the software
breakpoint instruction is detected (similar to the existing logic in booke.c
and e500_emulate.c) to restore software breakpoint functionality under Book3S
PR.
Signed-off-by: Mark Cave-Ayland <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Signed-off-by: Paul Mackerras <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions