From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC/RFT PATCH 0/2] spice-display locking fixes (cursors)?
Date: Mon, 20 Aug 2018 17:27:52 +0200 [thread overview]
Message-ID: <f5d4ea7c-0799-a30d-9afe-e5b83448011d@redhat.com> (raw)
In-Reply-To: <20180720063109.4631-1-pbonzini@redhat.com>
On 20/07/2018 08:31, Paolo Bonzini wrote:
> The first issue was found by Coverity and should be trivial. The second
> however made me wonder how to test the code and whether it has ever
> worked, because in theory it should be an instant deadlock whenever
> qemu_spice_cursor_refresh_bh is called.
>
> So I'm looking for help. In fact, the changes are not tested beyond
> compilation.
>
> Paolo
>
> Paolo Bonzini (2):
> spice-display: access ptr_x/ptr_y under Mutex
> spice-display: fix qemu_spice_cursor_refresh_bh locking
>
> ui/spice-display.c | 37 +++++++++++++++++++++++++------------
> 1 file changed, 25 insertions(+), 12 deletions(-)
>
Ping?
Paolo
next prev parent reply other threads:[~2018-08-20 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 6:31 [Qemu-devel] [RFC/RFT PATCH 0/2] spice-display locking fixes (cursors)? Paolo Bonzini
2018-07-20 6:31 ` [Qemu-devel] [PATCH 1/2] spice-display: access ptr_x/ptr_y under Mutex Paolo Bonzini
2018-07-20 6:31 ` [Qemu-devel] [PATCH 2/2] spice-display: fix qemu_spice_cursor_refresh_bh locking Paolo Bonzini
2018-08-20 15:27 ` Paolo Bonzini [this message]
2018-08-20 16:25 ` [Qemu-devel] [RFC/RFT PATCH 0/2] spice-display locking fixes (cursors)? Marc-André Lureau
2018-08-21 5:43 ` Gerd Hoffmann
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=f5d4ea7c-0799-a30d-9afe-e5b83448011d@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).