path: root/gdbstub.c
diff options
authorPaolo Bonzini <pbonzini@redhat.com>2015-08-18 06:52:09 -0700
committerPaolo Bonzini <pbonzini@redhat.com>2015-09-09 15:34:54 +0200
commit9102dedaa1ee1e89ce4a81283c403ff4928e9ef9 (patch)
treed98546ef77e276c3afea8397fd76c1e0d46d1922 /gdbstub.c
parentaed807c8e2bf009b2c6a35490d4fd4383887221d (diff)
use qemu_cpu_kick instead of cpu_exit or qemu_cpu_kick_thread
Use the same API to trigger interruption of a CPU, no matter if under TCG or KVM. There is no difference: these calls come from the CPU thread, so the qemu_cpu_kick calls will send a signal to the running thread and it will be processed synchronously, just like a call to cpu_exit. The only difference is in the overhead, but neither call to cpu_exit (now qemu_cpu_kick) is in a hot path. Reviewed-by: Richard Henderson <rth@twiddle.net> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'gdbstub.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/gdbstub.c b/gdbstub.c
index ffe7e6efb2..a5a173ab45 100644
--- a/gdbstub.c
+++ b/gdbstub.c
@@ -1362,7 +1362,7 @@ void gdb_do_syscall(gdb_syscall_complete_cb cb, const char *fmt, ...)
is still in the running state, which can cause packets to be dropped
and state transition 'T' packets to be sent while the syscall is still
being processed. */
- cpu_exit(s->c_cpu);
+ qemu_cpu_kick(s->c_cpu);