All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [virtio-dev] [PATCH] Add virtio gpu device specification.
Date: Tue, 10 May 2016 13:25:37 +0200	[thread overview]
Message-ID: <1462879537.8035.53.camel@redhat.com> (raw)
In-Reply-To: <1462874939.8035.52.camel@redhat.com>

  Hi,

> > > Rendered versions are available here:
> > >   https://www.kraxel.org/virtio/virtio-v1.0-cs03-virtio-gpu.pdf
> > >   https://www.kraxel.org/virtio/virtio-v1.0-cs03-virtio-gpu.html#x1-2800007

> > I guess a non-fenced command only completes when the operation has
> > finished, too (so that a meaningful success/error value can be
> > produced)?
> 
> When stuff is processed asynchronously the command can complete before
> the operation actually completed.  Current qemu implementation does that
> only in 3d mode, when offloading stuff to the hardware (and verifies
> stuff beforehand, so if you try to kick 3d rendering with an invalid
> context id qemu will throw an error).
> 
> I'll try to make that more clear in the text.

Updated now.

cheers,
  Gerd

  reply	other threads:[~2016-05-10 11:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 13:05 [Qemu-devel] [PATCH] Add virtio gpu device specification Gerd Hoffmann
2016-05-09 14:43 ` [Qemu-devel] [virtio-dev] " Stefan Hajnoczi
2016-05-10 10:08   ` Gerd Hoffmann
2016-05-10 11:25     ` Gerd Hoffmann [this message]
2018-06-20  3:15       ` Michael S. Tsirkin
2018-06-20  3:15         ` [Qemu-devel] " Michael S. Tsirkin
2018-06-27  6:15         ` Gerd Hoffmann
2018-06-27  6:15           ` [Qemu-devel] " Gerd Hoffmann
2018-06-27 18:56           ` Michael S. Tsirkin
2018-06-27 18:56             ` [Qemu-devel] " Michael S. Tsirkin

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=1462879537.8035.53.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.