diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2015-08-18 06:52:09 -0700 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-09-09 15:34:54 +0200 |
| commit | 9102dedaa1ee1e89ce4a81283c403ff4928e9ef9 (patch) | |
| tree | d98546ef77e276c3afea8397fd76c1e0d46d1922 /qobject | |
| parent | aed807c8e2bf009b2c6a35490d4fd4383887221d (diff) | |
| download | qemu-9102dedaa1ee1e89ce4a81283c403ff4928e9ef9.zip qemu-9102dedaa1ee1e89ce4a81283c403ff4928e9ef9.tar.gz qemu-9102dedaa1ee1e89ce4a81283c403ff4928e9ef9.tar.bz2 | |
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 'qobject')
0 files changed, 0 insertions, 0 deletions