summaryrefslogtreecommitdiffstats
path: root/server
Commit message (Collapse)AuthorAgeFilesLines
...
* server/inputs: return NULL on alloc_buf request for too large messageAlon Levy2010-12-071-0/+4
|
* server/red_channel: error channel if alloc_msg_buf fails (returns NULL)Alon Levy2010-12-071-0/+5
|
* server/inputs_channel: better protection from channel disconnection on ↵Alon Levy2010-12-071-1/+1
| | | | keyboard modifiers callback
* server/red_channel: add red_channel_is_connectedAlon Levy2010-12-072-0/+7
|
* server/inputs_channel: remove unused declaration in inputs_channel.hAlon Levy2010-12-071-1/+0
|
* server/inputs_channel: s/inputs_channel/g_inputs_channel/Alon Levy2010-12-071-17/+22
|
* server/inputs_channel: initialize inputs_channel to NULLAlon Levy2010-12-071-1/+1
|
* server: reds/inputs_channel: move some structs to inputs_channelAlon Levy2010-12-072-12/+12
|
* server: inputs_channel: use red_channelAlon Levy2010-12-071-282/+125
|
* server: red_channel: add optional parser and separate incoming/outgoing ↵Alon Levy2010-12-072-3/+107
| | | | error handlers for later inputs/main channel usage
* server: inputs_channel: s/inputs_state/inputs_channel/Alon Levy2010-12-071-51/+46
|
* server: introduce inputs_channel, split from reds.cAlon Levy2010-12-075-545/+786
|
* server/reds: fix typoAlon Levy2010-12-071-5/+5
|
* smartcard: configure option --enable-smartcardAlon Levy2010-12-071-0/+11
|
* smartcard: server side (not enabled yet)Alon Levy2010-12-073-0/+574
|
* server: add spice_server_char_device_remove_interfaceAlon Levy2010-12-071-5/+14
|
* server: print subtype when adding CHAR_DEVICE interfacesAlon Levy2010-12-061-1/+1
|
* server: add static to spice_server_char_device_add_interfaceAlon Levy2010-12-061-1/+1
|
* server: fix print text on vdagent interface additionAlon Levy2010-12-061-1/+1
|
* server: add char_device.h header, use in reds.cAlon Levy2010-12-062-4/+12
|
* spice-experimental.h: add multiple include protectionAlon Levy2010-12-061-1/+7
|
* server/vdi_port (virtserial): always read dataAlon Levy2010-12-061-6/+13
| | | | | | | | | | | | We erronously ignored data from guest on the serial channel if no client is connected. This leads to an assert when the guest writes a second time, since there is still data unconsumed by us (the host). Fix by reading data anyway, and discarding it after parsing (and reading) whole messages from the guest. Net affect is that any messages the agent sends while no client is connected get discarded, but only full messages are discarded. This fixes an abort if booting a winxp guest with vdagent without a connected client.
* server: add char_device.h to Makefile.am for make distAlon Levy2010-12-021-0/+1
|
* server/tests: add test_display_no_sslAlon Levy2010-11-304-50/+588
| | | | | | | | | | updates taken from spice vga mode updates, i.e. non cacheable, glz compressed (depends on whatever settings you apply to the server) opaque draw operations. + completed the SpiceCoreInterface implementation (timers) v1->v2: removed test_util.c (Hans) replaced mallocz with calloc (Hans)
* server/tests: Makefile.am fixesAlon Levy2010-11-301-2/+2
| | | | | * don't install tests on make install * don't forget anything for make dist tarball
* add .gitignore for testsAlon Levy2010-11-301-0/+4
|
* server/reds: zap unsetting of QEMU_AUDIO_DRVAlon Levy2010-11-081-1/+0
|
* gitignore: add generated_*, vim temps, pycAlon Levy2010-11-081-0/+3
|
* reds: remove needless buffer in InputsStateAlon Levy2010-11-081-3/+0
|
* server: tests: add basic tests with working do nothing serverAlon Levy2010-11-088-0/+293
|
* Release 0.6.30.6.3Hans de Goede2010-10-181-1/+1
|
* Bump version to 0.6.20.6.2Hans de Goede2010-10-181-1/+1
|
* server: remove useless agent send_tokensHans de Goede2010-10-161-32/+5
| | | | | | | | We are keeping track of tokens for sending agent data to the client, but the client send an initial value of ~0, and never gives us new send tokens so this is all rather useless -> remove it. Note that it is kept in the migration data struct for compatibility reasons.
* Call read_from_vdi_port() from vdi_read_buf_release()Hans de Goede2010-10-151-2/+12
| | | | | | | | | | | | | | | | | | | | | | | read_from_vdi_port(), called from vdagent_char_device_wakeup() may fail to consume all data because no buffers are available in the read_bufs ring. When this happens we would fail to ever read more data from the agent on the guest as the port is throttled and stays throttled until we've consumed all data from the current buffer. This patch re-enables the call to read_from_vdi_port() from vdi_read_buf_release(), so that we will try the read again when space becomes available in the read_bufs ring. Together with another nasty hack in the linux guest virtio_console driver, where it waits for a write to be acked by the host before continuing with the next one, this can lead to a linux guest getting stuck / hang (until the write is read by the spice-server which never happens becaus of the above issues). Note that even with this patch, the guest will still gets stuck due to a bug in watch_update_mask in spice-core in qemu, which causes writing to the client to never resume once it blocked. A patch for this has been submitted to qemu.
* server: always call read_from_vdi_port() in a while loopHans de Goede2010-10-151-2/+6
| | | | | | | | | | | | | | | | | | | | | | read_from_vdi_port() MUST always be called in a while loop until it returns 0. This is needed because it can cause new data available events and its recursion protection causes those to get lost. Calling it until it returns 0 ensures that all data has been consumed. Example scenario where we can fail to read the available data otherwise: - server/reds.c: vdagent_char_device_wakeup get called by hw/spice-vmc.c because data has arrived from the guest, - hw/spice-vmc.c: vmc_read get calls - If the vmc_read call depletes the current buffer it calls virtio_serial_throttle_port(&svc->port, false) - This causes vmc_have_data to get called, which if in the mean time another buffer has arrived causes vdagent_char_device_wakeup to gets called again (so recursively) - vdagent_char_device_wakeup is protected against recursive calling and ignores the second call (a nasty hack) - if no other data arrives, the arrived data will not get read
* Don't crash when a client disconnects while there were pending writesHans de Goede2010-10-151-1/+1
|
* server: add channel notifications.Gerd Hoffmann2010-10-123-4/+48
| | | | | | | | | | | | | This patch adds a channel event callback to the spice core interface. This new callback will be called for three events: (1) A new connection has been established. (2) The channel is ready (i.e. authentication is done, link message verification passed all tests, channel is ready to use). (3) Channel was disconnected. Qemu will use this to send notifications to the management app.
* server: Handle self_image in localize_bitmapAlexander Larsson2010-09-211-9/+16
| | | | | | When drawing a drawable with a NULL src bitmap that means we should be using the previously generated self_bitmap. Not doing this causes a segfault due to accessing the NULL.
* server: Handle NULL image in red_update_streamableAlexander Larsson2010-09-211-1/+2
| | | | A NULL src bitmap means self_bitmap, which is not a stream, so abort.
* server: Use the right image size for self_bitmapAlexander Larsson2010-09-211-2/+2
| | | | | | | The self_bitmap is the size of self_bitmap_area, not the bbox. This is especially important since we later copy the self_bitmap_area into the new bitmap, and if that is larger than bbox then we will overwrite random memory.
* server: Don't leak QUIC image chunksAlexander Larsson2010-09-211-0/+3
| | | | | red_put_image() needs to free the chunks for QUIC images, as we allocate these when creating the image.
* server: Ensure we flush the release pipe after an oomAlexander Larsson2010-09-201-0/+1
| | | | | | We really need to flush the ring to ensure that we push something on the release ring. If we don't do this and the ring is not pushed for other reasons we will timeout in the guest driver waiting for the ring.
* Release more drawables on OOMAlexander Larsson2010-09-201-1/+1
| | | | | | | | We've changed how resources are released so they are now being freed continuosly, rather than on OOM, since we want to free as early possible to avoid fragmentation. So, OOM situations should be a bit less common now and signify a real memory shortage, so we should try to free up more resources.
* fix palette handling for 0.4 compatGerd Hoffmann2010-09-141-43/+56
| | | | | spice 0.4 guests pass 16bpp palette colors when running in a 16bpp video mode. Convert them to 32bpp.
* fix brush handling for 0.4 compatGerd Hoffmann2010-09-141-23/+38
| | | | | spice 0.4 guests pass 16bpp colors for brushes when running in a 16bpp video mode. Convert them to 32bpp.
* move command flags handling to the qxl parserGerd Hoffmann2010-09-143-14/+18
| | | | | Pass through command flags to the qxl parser, so we can hide all compat bits for spice 0.4 within the qxl parser.
* server: avoid creating a stream from traces more than once for the same drawableYonit Halperin2010-09-021-5/+10
| | | | could have caused ASSERT(!drawable->stream) in red_create_stream
* Add API to turn on backwards compatibility modeAlexander Larsson2010-09-022-0/+33
| | | | | | | | | | | | | | | | | | When upgrading a cluster of machines you typically do this by upgrading a set of machines at a time, making the new machines run the new software version, but in a fashion compatible with the old versions (in terms of e.g. migration). Then when all machines are upgrades, any new features in the new version can be enabled. This API allows qemu to limit the set of features that spice uses to those compatible with an older version, in order to do an upgrade like this. Right now it doesn't really do much, since we don't keep compat with 0.4.0 atm (although that may be added later). There is no guarantee that any future version of spice support being compatible with any previous version. However, we will always support compatibility with the previous major version so that clusters can be upgraded step by step.
* qxl parser: complete parsing of QXLCompatDrawable structsGerd Hoffmann2010-08-311-0/+14
|
* server: red_current_add_equal - don't push a drawable to the middle of the ↵Yonit Halperin2010-08-311-1/+13
| | | | | | | pipe if it depends on surfaces. This will prevent: 1) rendering problems (commands sent to the client in the wrong order) 2) sending commands for surfaces that haven't been created yet on the client side.