From: Daniel Vetter <daniel@ffwll.ch>
To: Yi Xie <yixie@google.com>
Cc: hamohammed.sa@gmail.com, rodrigosiqueiramelo@gmail.com,
dri-devel@lists.freedesktop.org, melissa.srw@gmail.com,
lepton@google.com
Subject: Re: [PATCH] drm/vkms: Add a DRM render node to vkms
Date: Thu, 5 Jan 2023 12:36:54 +0100 [thread overview]
Message-ID: <Y7a2Viw/1RUNCGkD@phenom.ffwll.local> (raw)
In-Reply-To: <20230105052325.514970-1-yixie@google.com>
On Thu, Jan 05, 2023 at 02:23:25PM +0900, Yi Xie wrote:
> Some libraries including Mesa and virglrenderer require a render node to
> fully function. By adding a render node to vkms those libraries will
> work properly, supporting use cases like running crosvm with virgl GPU
> support via llvmpipe on a headless virtual machine.
This is what vgem exists for. More or less at least ... I'm honestly not
really understanding what you're trying to fix here, it sounds a bit like
userspace being stupid.
-Daniel
>
> Signed-off-by: Yi Xie <yixie@google.com>
> ---
> drivers/gpu/drm/vkms/vkms_drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/vkms/vkms_drv.c b/drivers/gpu/drm/vkms/vkms_drv.c
> index 293dbca50c31..8eea5d4dece8 100644
> --- a/drivers/gpu/drm/vkms/vkms_drv.c
> +++ b/drivers/gpu/drm/vkms/vkms_drv.c
> @@ -113,7 +113,7 @@ static void vkms_config_debugfs_init(struct drm_minor *minor)
> }
>
> static const struct drm_driver vkms_driver = {
> - .driver_features = DRIVER_MODESET | DRIVER_ATOMIC | DRIVER_GEM,
> + .driver_features = DRIVER_MODESET | DRIVER_ATOMIC | DRIVER_GEM | DRIVER_RENDER,
> .release = vkms_release,
> .fops = &vkms_driver_fops,
> DRM_GEM_SHMEM_DRIVER_OPS,
> --
> 2.39.0.314.g84b9a713c41-goog
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-01-05 11:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 5:23 [PATCH] drm/vkms: Add a DRM render node to vkms Yi Xie
2023-01-05 10:49 ` Simon Ser
2023-01-05 11:36 ` Daniel Vetter [this message]
2023-01-05 12:52 ` Yi Xie
2023-01-05 13:48 ` Daniel Vetter
2023-01-05 14:10 ` Yi Xie
2023-01-05 14:16 ` Daniel Vetter
2023-01-05 15:16 ` Yi Xie
2023-01-05 15:35 ` Daniel Vetter
2023-01-05 21:40 ` Tao Wu(吴涛@Eng)
2023-01-06 9:54 ` Daniel Vetter
2023-01-06 10:02 ` Yi Xie
2023-01-06 20:10 ` Daniel Vetter
2023-01-06 22:28 ` Tao Wu(吴涛@Eng)
2023-01-07 10:45 ` Simon Ser
2023-01-08 5:09 ` Tao Wu(吴涛@Eng)
2023-01-09 9:36 ` Michel Dänzer
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=Y7a2Viw/1RUNCGkD@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=lepton@google.com \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=yixie@google.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