Signed-off-by: Frediano Ziglio <fzig...@redhat.com> --- docs/spice_threading_model.txt | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/docs/spice_threading_model.txt b/docs/spice_threading_model.txt index 9351141c8..25a3a030c 100644 --- a/docs/spice_threading_model.txt +++ b/docs/spice_threading_model.txt @@ -39,6 +39,14 @@ connect, disconnect and migrate. Connect and migrate are asynchronous (the job is done while the current thread is doing something else) while disconnect is synchronous (the main thread will wait for termination). +One aspect to take into consideration is the event scheduling. SPICE uses some +`SpiceCoreInterface` to handle events. As the events will be handled from a +thread based on the core interface you have to use the correct core. Each +channel has an associated core interface which can be retrieved using +`red_channel_get_core_interface`. There's also a main core interface you can get +using `reds_get_core_interface`. `reds_core_timer_*` and `reds_core_watch_*` +functions use the main core interface. + Reference counting and ownership -------------------------------- -> pointer -- 2.20.1 _______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/spice-devel
