From: Gerd Hoffmann <kraxel@redhat.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>
Cc: Dongwon Kim <dongwon.kim@intel.com>,
dri-devel@lists.freedesktop.org,
Tina Zhang <tina.zhang@intel.com>
Subject: Re: [PATCH v1 0/3] drm/virtio: Add a default synchronization mechanism for blobs
Date: Wed, 23 Jun 2021 14:13:54 +0200 [thread overview]
Message-ID: <20210623121354.raajeo2fy6lj7gcx@sirius.home.kraxel.org> (raw)
In-Reply-To: <20210610232456.671905-1-vivek.kasireddy@intel.com>
On Thu, Jun 10, 2021 at 04:24:53PM -0700, Vivek Kasireddy wrote:
> This 3 patch series is the counterpart for this other series:
> https://lists.nongnu.org/archive/html/qemu-devel/2021-06/msg02906.html
>
> It makes it possible for the Guest to wait until the Host has
> completely consumed its FB before reusing it again thereby ensuring
> that both the parties don't access it at the same time.
>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Dongwon Kim <dongwon.kim@intel.com>
> Cc: Tina Zhang <tina.zhang@intel.com>
>
> Vivek Kasireddy (3):
> drm/virtio: Add fences for Guest blobs
> drm/virtio: Prepare resource_flush to accept a fence
> drm/virtio: Add the fence in resource_flush if present
Pushed to drm-misc-next.
thanks,
Gerd
prev parent reply other threads:[~2021-06-23 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 23:24 [PATCH v1 0/3] drm/virtio: Add a default synchronization mechanism for blobs Vivek Kasireddy
2021-06-10 23:24 ` [PATCH v1 1/3] drm/virtio: Add fences for Guest blobs Vivek Kasireddy
2021-06-10 23:24 ` [PATCH v1 2/3] drm/virtio: Prepare resource_flush to accept a fence Vivek Kasireddy
2021-06-10 23:24 ` [PATCH v1 3/3] drm/virtio: Add the fence in resource_flush if present Vivek Kasireddy
2021-06-23 12:13 ` 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=20210623121354.raajeo2fy6lj7gcx@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tina.zhang@intel.com \
--cc=vivek.kasireddy@intel.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).