[Spice-devel] [spice-server PATCH 2/2] display seamless migration: no need to trace the generation of the primary surface

2012-11-05 Thread Yonit Halperin
We no longer process destroy_primary or destroy_surfaces while waiting for migration data. --- server/red_worker.c | 51 --- 1 files changed, 16 insertions(+), 35 deletions(-) diff --git a/server/red_worker.c b/server/red_worker.c index dd27872..4

[Spice-devel] [spice-server PATCH 1/2] display seamless migration: don't process both cmd ring and dispatcher queue till migration data is received

2012-11-05 Thread Yonit Halperin
fix: rhbz#866929 At migration destination side, we need to restore the client's surfaces state, before sending surfaces related messages. Before this patch, we stopped the processing of only the cmd ring, till migration data arrived. However, some QXL_IOs require reading and rendering the cmd rin

[Spice-devel] [RFC] [PATCH vd_agent] DND: Add drag-and-drop support

2012-11-05 Thread Dunrong Huang
For now, there are two types of messages needed to be handled 1) VD_AGENT_DND_START: when user drags a file and drop to spice client, spice client will send this message to notify guest agent to prepare for receiving file, file name and file size are included in message's data. 2) VD_AGENT_DND_DA

[Spice-devel] [RFC] [PATCH spice-gtk 4/4] DND: Set a maximum allowed file size

2012-11-05 Thread Dunrong Huang
Because of some technological reason, e.g. a progress bar that allows user to cancels file transfer has not been done. We have to specify a maximum allowed file size so file content will not consume too much memory. Signed-off-by: Dunrong Huang --- gtk/spice-dnd.c | 22 ++ 1

[Spice-devel] [RFC] [PATCH spice-gtk 3/4] DND: handle "drag-data-received" signal

2012-11-05 Thread Dunrong Huang
When user drags a file to SpiceDisplay and drops it, a signal named "drag-data-received" will be emitted, the signal will be received by SpiceDisplay, then our signal handler will receive data which contains file path, and call spice_dnd_process() to transfer file to guest. Signed-off-by: Dunrong

[Spice-devel] [RFC] [PATCH spice-protocol] DND: Add VD_AGENT_DND_*

2012-11-05 Thread Dunrong Huang
For now, there are two types of DND messages 1) VD_AGENT_DND_START: when user drags a file and drop to spice client, spice client will send this message to notify guest agent to prepare for receiving file. 2) VD_AGENT_DND_DATA: is used to transfer file content. Signed-off-by: Dunrong Hua

[Spice-devel] [RFC] [PATCH spice-gtk 2/4] DND: Add spice-dnd.c

2012-11-05 Thread Dunrong Huang
The file provides a API spice_dnd_process for processing DND message, e.g. sending DND start message. After received "drag-data-received" signal, SpiceDisplay could call this API to sending dnd message. Signed-off-by: Dunrong Huang --- gtk/Makefile.am | 1 + gtk/map-file|

[Spice-devel] [RFC] [PATCH spice-gtk 1/4] DND: Add spice_main_dnd_*() for sending dnd message to guest

2012-11-05 Thread Dunrong Huang
These functions could send dnd message to guest. For now, there are two types of messages: 1) VD_AGENT_DND_START: when user drags a file and drop to spice client, spice client will send this message to notify guest agent to prepare for receiving file, file's name and size are included

[Spice-devel] [RFC] [PATCH spice-gtk 0/4] simply implement of file drag-and-drop

2012-11-05 Thread Dunrong Huang
These patches simply implement file drag-and-drop from client to guest. There are some TODOs needed to be done: * transfer multiple files and directories * check whether guest has enough space to store file * a progress bar that allows user to cancels file transfer, since we always pre-c