From: Robert Foss <robert.foss@collabora.com>
To: Gurchetan Singh <gurchetansingh@chromium.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] virtgpu: Update kernel header
Date: Mon, 4 Mar 2019 09:25:57 +0100 [thread overview]
Message-ID: <f362416f-3526-ffb4-e782-002bc194891a@collabora.com> (raw)
In-Reply-To: <20190228005237.2149-1-gurchetansingh@chromium.org>
Hey Gurchetan,
Thanks for sending this in!
Reviewed-by: Robert Foss <robert.foss@collabora.com>
On 2/28/19 1:52 AM, Gurchetan Singh wrote:
> Generated using make headers_install.
>
> This brings in the in/out fence support for explicit
> synchronization.
>
> v2: don't use experimental kernel branch
>
> Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
> ---
> include/drm/virtgpu_drm.h | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/include/drm/virtgpu_drm.h b/include/drm/virtgpu_drm.h
> index 9a781f06..f06a789f 100644
> --- a/include/drm/virtgpu_drm.h
> +++ b/include/drm/virtgpu_drm.h
> @@ -47,6 +47,13 @@ extern "C" {
> #define DRM_VIRTGPU_WAIT 0x08
> #define DRM_VIRTGPU_GET_CAPS 0x09
>
> +#define VIRTGPU_EXECBUF_FENCE_FD_IN 0x01
> +#define VIRTGPU_EXECBUF_FENCE_FD_OUT 0x02
> +#define VIRTGPU_EXECBUF_FLAGS (\
> + VIRTGPU_EXECBUF_FENCE_FD_IN |\
> + VIRTGPU_EXECBUF_FENCE_FD_OUT |\
> + 0)
> +
> struct drm_virtgpu_map {
> __u64 offset; /* use for mmap system call */
> __u32 handle;
> @@ -54,12 +61,12 @@ struct drm_virtgpu_map {
> };
>
> struct drm_virtgpu_execbuffer {
> - __u32 flags; /* for future use */
> + __u32 flags;
> __u32 size;
> __u64 command; /* void* */
> __u64 bo_handles;
> __u32 num_bo_handles;
> - __u32 pad;
> + __s32 fence_fd; /* in/out fence fd (see VIRTGPU_EXECBUF_FENCE_FD_IN/OUT) */
> };
>
> #define VIRTGPU_PARAM_3D_FEATURES 1 /* do we have 3D features in the hw */
> @@ -137,7 +144,7 @@ struct drm_virtgpu_get_caps {
> DRM_IOWR(DRM_COMMAND_BASE + DRM_VIRTGPU_MAP, struct drm_virtgpu_map)
>
> #define DRM_IOCTL_VIRTGPU_EXECBUFFER \
> - DRM_IOW(DRM_COMMAND_BASE + DRM_VIRTGPU_EXECBUFFER,\
> + DRM_IOWR(DRM_COMMAND_BASE + DRM_VIRTGPU_EXECBUFFER,\
> struct drm_virtgpu_execbuffer)
>
> #define DRM_IOCTL_VIRTGPU_GETPARAM \
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-04 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 0:29 [PATCH] virtgpu: Update kernel header Gurchetan Singh
2019-02-28 0:52 ` Gurchetan Singh
2019-03-04 8:25 ` Robert Foss [this message]
2019-04-01 23:01 ` 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=f362416f-3526-ffb4-e782-002bc194891a@collabora.com \
--to=robert.foss@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.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