From: Gerd Hoffmann <kraxel@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio-gpu: cursor update not in sync with resource update
Date: Tue, 15 Sep 2015 08:20:07 +0200 [thread overview]
Message-ID: <1442298007.2895.0.camel@redhat.com> (raw)
In-Reply-To: <CAPM=9txTSEM4rODq+5Qusx9y2M18eTP8+3ba5aG4rOqg7PjJFw@mail.gmail.com>
Hi,
> >> if (!ret) {
> >> reservation_object_add_excl_fence(qobj->tbo.resv,
> >> &fence->f);
> >> virtio_gpu_object_wait(qobj, false);
> >> }
> >>
> >> before moving the cursor, shouldn't that suffice?
> >>
> >> Do we fail the transfer sometimes?
> >
> >
> > That's apparently not in Gerd tree.
>
> Interesting, I'm not sure where this got lost,
Probably fallen through the cracks with the recent fence fixups.
I've added it back.
cheers,
Gerd
prev parent reply other threads:[~2015-09-15 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 12:40 [Qemu-devel] virtio-gpu: cursor update not in sync with resource update Marc-André Lureau
2015-09-14 14:06 ` Gerd Hoffmann
2015-09-14 15:17 ` Marc-André Lureau
2015-09-14 21:08 ` Dave Airlie
2015-09-14 21:14 ` Marc-André Lureau
2015-09-14 21:18 ` Dave Airlie
2015-09-15 6:20 ` Gerd Hoffmann [this message]
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=1442298007.2895.0.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@gmail.com \
--cc=marcandre.lureau@gmail.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).