qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Cc: hdegoede@redhat.com, uril@redhat.com, gleb@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/4] qxl: implement vga mode without locks
Date: Wed, 16 Mar 2011 17:52:45 +0200	[thread overview]
Message-ID: <1300290769-31155-1-git-send-email-alevy@redhat.com> (raw)

v2->v3 changes: (Hans de Goede)
 * minor review fixes
 * fix compilation of qemu with --enable-spice with a target which does
  not have a qxl device

v1->v2 changes:
 * patch 4 rewrite: instead of todos implemented usage of pipe for cursor_set
  and cursor_move.
 * small fixes: (Hans de Goede)
  * fix introducing function in patch 1 and renaming it in patch 2.
   (s/qxl_create_vcpu_to_iothread_pipe/qxl_create_server_to_iothread_pipe/)
  * move prototype defined in patch 1 but used in patch 2 to patch 2.
   (qxl_vga_mode_get_command)

This patchset removes all uses of unlock/lock in qxl and spice code.

It does this by reimplementing the one path that required a lock from the
spice-server thread, namely interface_get_command when in vga mode or running
without a qxl device.

Incidentaly it fixes the assert(cpu_single_env) that happen in the unrelated
qemu-kvm repository, because we never drop the global lock in io vmexits.

Tested with winxp 32 bit and linux 64 bit vms, including changes between vga
mode and qxl mode using chvt. Also tested -sdl and -vnc together with -spice.


Alon Levy (3):
  qxl/spice-display: move pipe to ssd
  qxl/spice: remove qemu_mutex_{un,}lock_iothread around dispatcher
  hw/qxl-render: drop cursor locks, replace with pipe

Uri Lublin (1):
  qxl: implement get_command in vga mode without locks

 hw/qxl-render.c    |   25 ++++---
 hw/qxl.c           |  193 +++++++++++++++++++++++++++++++++++++++++-----------
 hw/qxl.h           |    8 +-
 ui/spice-display.c |  115 +++++++++++++++++++++++++------
 ui/spice-display.h |   35 ++++++++++
 5 files changed, 300 insertions(+), 76 deletions(-)

-- 
1.7.4.1

             reply	other threads:[~2011-03-16 15:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 15:52 Alon Levy [this message]
2011-03-16 15:52 ` [Qemu-devel] [PATCH v3 1/4] qxl/spice-display: move pipe to ssd Alon Levy
2011-03-16 15:58   ` Hans de Goede
2011-03-16 16:39   ` Jes Sorensen
2011-03-16 16:42     ` Alon Levy
2011-03-16 15:52 ` [Qemu-devel] [PATCH v3 2/4] qxl: implement get_command in vga mode without locks Alon Levy
2011-03-16 16:00   ` [Qemu-devel] " Hans de Goede
2011-03-16 15:52 ` [Qemu-devel] [PATCH v3 3/4] qxl/spice: remove qemu_mutex_{un, }lock_iothread around dispatcher Alon Levy
2011-03-16 16:01   ` [Qemu-devel] " Hans de Goede
2011-03-16 15:52 ` [Qemu-devel] [PATCH v3 4/4] hw/qxl-render: drop cursor locks, replace with pipe Alon Levy
2011-03-16 16:02   ` [Qemu-devel] " Hans de Goede
2011-03-16 16:48   ` [Qemu-devel] " Jes Sorensen
2011-03-17  9:32     ` Alon Levy
2011-03-17  9:48       ` Jes Sorensen
2011-03-17 10:27         ` Alon Levy
2011-03-17 10:29           ` Jes Sorensen
2011-03-17 10:45             ` Alon Levy
2011-03-17 14:19               ` Jes Sorensen
2011-03-17 15:08                 ` Alon Levy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1300290769-31155-1-git-send-email-alevy@redhat.com \
    --to=alevy@redhat.com \
    --cc=gleb@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=uril@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).