From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org, virtio@lists.oasis-open.org
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Gerd Hoffmann <kraxel@redhat.com>,
David Airlie <airlied@redhat.com>
Subject: [PATCH 0/3] virtio-gpu api: memory and resource management
Date: Wed, 10 Apr 2019 13:42:24 +0200 [thread overview]
Message-ID: <20190410114227.25846-1-kraxel@redhat.com> (raw)
Hi folks,
Revisited the old VIRTIO_GPU_CMD_RESOURCE_CREATE_V2 approach and figured
this is maybe not the best way to go forward. I think it is much more
useful to separate memory and resource management (see patch #2).
VIRTIO_GPU_CMD_RESOURCE_CREATE_V2 is still there (see patch #3).
For now I have the virtio protocol changes only, looking for comments
on the idea. Will try add support to the virtio-gpu.ko driver and qemu
next. Support in virglrenderer and the virtio-gpu ioctl interface is
likewise on the TODO list still.
cheers,
Gerd
Gerd Hoffmann (3):
virtio-gpu api: comment feature flags
virtio-gpu api: VIRTIO_GPU_F_MEMORY
virtio-gpu api: VIRTIO_GPU_F_RESSOURCE_V2
include/uapi/linux/virtio_gpu.h | 81 ++++++++++++++++++++++++++++++++-
1 file changed, 79 insertions(+), 2 deletions(-)
--
2.18.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-04-10 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 11:42 Gerd Hoffmann [this message]
2019-04-10 11:42 ` [PATCH 1/3] virtio-gpu api: comment feature flags Gerd Hoffmann
2019-04-11 1:03 ` Gurchetan Singh
2019-04-10 11:42 ` [PATCH 2/3] virtio-gpu api: VIRTIO_GPU_F_MEMORY Gerd Hoffmann
2019-04-10 11:42 ` [PATCH 3/3] virtio-gpu api: VIRTIO_GPU_F_RESSOURCE_V2 Gerd Hoffmann
2019-04-11 1:06 ` Gurchetan Singh
2019-04-11 5:03 ` Gerd Hoffmann
2019-04-12 1:36 ` Gurchetan Singh
2019-04-12 5:49 ` Gerd Hoffmann
2019-04-12 23:34 ` Chia-I Wu
2019-04-17 9:57 ` Gerd Hoffmann
2019-04-17 18:06 ` Chia-I Wu
2019-04-23 0:12 ` Gurchetan Singh
2019-04-13 0:49 ` 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=20190410114227.25846-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=mst@redhat.com \
--cc=tomeu.vizoso@collabora.com \
--cc=virtio@lists.oasis-open.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