All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gurchetan Singh <gurchetansingh@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: kraxel@redhat.com
Subject: [PATCH v3 07/19] drm/virtgpu api: cross-device feature
Date: Wed, 16 Sep 2020 17:08:26 -0700	[thread overview]
Message-ID: <20200917000838.735-7-gurchetansingh@chromium.org> (raw)
In-Reply-To: <20200917000838.735-1-gurchetansingh@chromium.org>

This feature was recently added to virtio-gpu, lets make
it userspace queryable. It's an error to use
BLOB_FLAG_USE_CROSS_DEVICE when this feature is not present.

Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Acked-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
---
 include/uapi/drm/virtgpu_drm.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/uapi/drm/virtgpu_drm.h b/include/uapi/drm/virtgpu_drm.h
index e1b1518f9acc5..b9ec26e9c6463 100644
--- a/include/uapi/drm/virtgpu_drm.h
+++ b/include/uapi/drm/virtgpu_drm.h
@@ -74,6 +74,7 @@ struct drm_virtgpu_execbuffer {
 #define VIRTGPU_PARAM_CAPSET_QUERY_FIX 2 /* do we have the capset fix */
 #define VIRTGPU_PARAM_RESOURCE_BLOB 3 /* DRM_VIRTGPU_RESOURCE_CREATE_BLOB */
 #define VIRTGPU_PARAM_HOST_VISIBLE 4 /* Host blob resources are mappable */
+#define VIRTGPU_PARAM_CROSS_DEVICE 5 /* Cross virtio-device resource sharing  */
 
 struct drm_virtgpu_getparam {
 	__u64 param;
-- 
2.26.2

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-09-17  0:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  0:08 [PATCH v3 01/19] drm/virtio: blob prep: refactor getting pages and attaching backing Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 02/19] drm/virtio: blob prep: make CPU responses more generic Gurchetan Singh
2020-09-17  9:33   ` Gerd Hoffmann
2020-09-17  0:08 ` [PATCH v3 03/19] virtio-gpu api: blob resources Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 04/19] virtio-gpu api: host visible feature Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 05/19] drm/virtgpu api: blob resources Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 06/19] drm/virtgpu api: host visible feature Gurchetan Singh
2020-09-17  0:08 ` Gurchetan Singh [this message]
2020-09-17  0:08 ` [PATCH v3 08/19] drm/virtio: implement blob resources: probe for the feature Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 09/19] drm/virtio: implement blob resources: probe for host visible region Gurchetan Singh
2020-09-17  9:40   ` Gerd Hoffmann
2020-09-17 22:25     ` [PATCH v4 " Gurchetan Singh
2020-09-17 22:27     ` [PATCH v3 " Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 10/19] drm/virtio: implement blob resources: expose virtio_gpu_resource_id_get Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 11/19] drm/virtio: implement blob resources: add new fields to internal structs Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 12/19] drm/virtio: implement blob resources: implement vram object Gurchetan Singh
2020-09-17  9:42   ` Gerd Hoffmann
2020-09-17  0:08 ` [PATCH v3 13/19] drm/virtio: implement blob resources: hypercall interface Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 14/19] drm/virtio: implement blob resources: blob display integration Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 15/19] drm/virtio: implement blob resources: refactor UUID code somewhat Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 16/19] drm/virtio: implement blob resources: fix stride discrepancy Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 17/19] drm/virtio: implement blob resources: report blob mem to userspace Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 18/19] drm/virtio: implement blob resources: resource create blob ioctl Gurchetan Singh
2020-09-17  0:08 ` [PATCH v3 19/19] drm/virtio: advertise features to userspace Gurchetan Singh

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=20200917000838.735-7-gurchetansingh@chromium.org \
    --to=gurchetansingh@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@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 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.