From: "Christian König" <christian.koenig@amd.com>
To: John Stultz <jstultz@google.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Jason Ekstrand <jason@jlekstrand.net>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
Chunming Zhou <david1.zhou@amd.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [RFC][PATCH 2/3] drm: vgem: Enable SYNCOBJ and SYNCOBJ_TIMELINE on vgem driver
Date: Tue, 12 Jul 2022 09:45:55 +0200 [thread overview]
Message-ID: <6e490429-e34c-fa51-c6d9-3315c4639d9d@amd.com> (raw)
In-Reply-To: <20220712042258.293010-2-jstultz@google.com>
Am 12.07.22 um 06:22 schrieb John Stultz:
> Allows for basic SYNCOBJ api testing, in environments
> like VMs where there may not be a supported drm driver.
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <mripard@kernel.org>
> Cc: Thomas Zimmermann <tzimmermann@suse.de>
> Cc: Jason Ekstrand <jason@jlekstrand.net>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Cc: Chunming Zhou <david1.zhou@amd.com>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: dri-devel@lists.freedesktop.org
> Signed-off-by: John Stultz <jstultz@google.com>
> ---
> drivers/gpu/drm/vgem/vgem_drv.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
> index c5e3e5457737..e5427d7399da 100644
> --- a/drivers/gpu/drm/vgem/vgem_drv.c
> +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> @@ -109,7 +109,8 @@ static struct drm_gem_object *vgem_gem_create_object(struct drm_device *dev, siz
> }
>
> static const struct drm_driver vgem_driver = {
> - .driver_features = DRIVER_GEM | DRIVER_RENDER,
> + .driver_features = DRIVER_GEM | DRIVER_RENDER |
> + DRIVER_SYNCOBJ | DRIVER_SYNCOBJ_TIMELINE,
Well that's rather surprising. I'm not an export on VGEM, but AFAIK you
need to adjust the CS interface to support that stuff as well.
Christian.
> .open = vgem_open,
> .postclose = vgem_postclose,
> .ioctls = vgem_ioctls,
next prev parent reply other threads:[~2022-07-12 7:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 4:22 [RFC][PATCH 1/3] drm: drm_syncobj: Add note in DOC about absolute timeout values John Stultz
2022-07-12 4:22 ` [RFC][PATCH 2/3] drm: vgem: Enable SYNCOBJ and SYNCOBJ_TIMELINE on vgem driver John Stultz
2022-07-12 7:45 ` Christian König [this message]
2022-07-12 16:50 ` John Stultz
2022-07-13 8:02 ` Christian König
2022-07-12 4:22 ` [RFC][PATCH 3/3] kselftest: Add drm_syncobj API test tool John Stultz
2022-07-12 7:43 ` Christian König
2022-07-12 15:52 ` John Stultz
2022-08-10 16:42 ` Daniel Vetter
2022-07-12 5:29 ` [RFC][PATCH 1/3] drm: drm_syncobj: Add note in DOC about absolute timeout values John Stultz
2022-07-12 7:40 ` Christian König
2022-07-12 15:48 ` John Stultz
2022-07-12 15:54 ` Christian König
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=6e490429-e34c-fa51-c6d9-3315c4639d9d@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=david1.zhou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®