Paolo Bonzini 9102dedaa1
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 >
2015-09-09 15:34:54 +02:00
2015-07-27 18:11:53 +03:00
2015-07-27 22:44:47 +03:00
2015-06-03 14:21:24 +03:00
2015-08-25 15:45:06 +01:00
2015-04-27 18:24:18 +02:00
2015-09-09 15:34:53 +02:00
2015-04-28 15:36:08 +02:00
2015-08-18 17:06:41 +01:00
2015-07-13 13:35:51 +01:00
2015-08-13 11:26:22 +01:00
2015-04-11 20:03:57 +10:00
2015-07-28 17:09:56 +01:00
2015-09-09 15:34:53 +02:00
2015-06-02 14:56:25 +01:00
2015-05-29 11:28:59 +01:00
2015-09-09 15:34:53 +02:00
2015-08-03 14:27:12 +00:00
2015-07-27 18:11:53 +03:00
2015-08-13 11:26:21 +01:00
2015-02-26 12:42:16 +01:00
2015-09-09 15:34:53 +02:00
2015-06-03 14:21:24 +03:00
2015-06-22 14:43:25 +01:00
2015-07-03 17:47:58 -03:00
2015-07-09 15:20:40 +02:00
2015-09-09 15:34:53 +02:00
2015-09-07 18:14:03 +02:00
2015-08-14 18:06:44 +01:00
2015-07-07 17:44:50 +02:00
2015-08-13 14:08:29 +03:00
2015-06-23 22:58:36 +02:00
2015-08-13 17:47:44 +01:00
2015-09-09 15:34:54 +02:00
2015-07-14 19:10:03 +02:00
2015-08-14 23:40:32 +02:00
2015-06-15 18:06:09 +01:00
2015-06-12 12:02:48 +02:00
2015-08-13 14:08:30 +03:00
2015-09-09 15:34:53 +02:00
2015-09-09 15:34:53 +02:00
2015-03-19 11:11:55 +03:00
2015-08-13 11:26:21 +01:00
2015-06-22 18:20:40 +02:00
2015-06-03 14:21:24 +03:00
2015-07-27 14:12:18 +01:00
2015-07-22 14:56:01 -06:00
2015-08-05 16:56:34 +03:00
2015-07-14 19:10:03 +02:00
2015-06-23 18:25:55 +01:00
2015-03-10 08:15:33 +03:00
2015-08-13 14:08:30 +03:00
9102dedaa1