use qemu_cpu_kick instead of cpu_exit or qemu_cpu_kick_thread
authorPaolo Bonzini <pbonzini@redhat.com>
Tue, 18 Aug 2015 13:52:09 +0000 (06:52 -0700)
committerPaolo Bonzini <pbonzini@redhat.com>
Wed, 9 Sep 2015 13:34:54 +0000 (15:34 +0200)
commit9102dedaa1ee1e89ce4a81283c403ff4928e9ef9
treed98546ef77e276c3afea8397fd76c1e0d46d1922
parentaed807c8e2bf009b2c6a35490d4fd4383887221d
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>
cpus.c
gdbstub.c
hw/ppc/spapr_rtas.c