From: Gurchetan Singh <gurchetansingh@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: Gurchetan Singh <gurchetansingh@chromium.org>,
kraxel@redhat.com, jbates@chromium.org
Subject: [PATCH v2 0/5] *** Delay context create cmd ***
Date: Thu, 13 Feb 2020 15:18:00 -0800 [thread overview]
Message-ID: <20200213231805.622-1-gurchetansingh@chromium.org> (raw)
Let's delay enqueuing the context creation command until the first 3D
ioctl, as we add more context types. This series is based on kraxel's
"[PATCH v3 0/4] drm/virtio: rework batching" patches.
Gurchetan Singh (5):
drm/virtio: use consistent names for drm_files
drm/virtio: factor out context create hyercall
drm/virtio: track whether or not a context has been initiated
drm/virtio: enqueue virtio_gpu_create_context after the first 3D ioctl
drm/virtio: add virtio_gpu_context_type
drivers/gpu/drm/virtio/virtgpu_drv.h | 1 +
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 55 +++++++++++++++++++++-----
drivers/gpu/drm/virtio/virtgpu_kms.c | 25 +++---------
3 files changed, 52 insertions(+), 29 deletions(-)
--
2.25.0.265.gbab2e86ba0-goog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-02-13 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 23:18 Gurchetan Singh [this message]
2020-02-13 23:18 ` [PATCH 1/5] drm/virtio: use consistent names for drm_files Gurchetan Singh
2020-02-13 23:18 ` [PATCH 2/5] drm/virtio: factor out context create hyercall Gurchetan Singh
2020-02-13 23:18 ` [PATCH 3/5] drm/virtio: track whether or not a context has been initiated Gurchetan Singh
2020-02-14 19:27 ` Chia-I Wu
2020-02-15 2:29 ` Gurchetan Singh
2020-02-15 4:29 ` Chia-I Wu
2020-02-13 23:18 ` [PATCH 4/5] drm/virtio: enqueue virtio_gpu_create_context after the first 3D ioctl Gurchetan Singh
2020-02-13 23:18 ` [PATCH 5/5] drm/virtio: add virtio_gpu_context_type 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=20200213231805.622-1-gurchetansingh@chromium.org \
--to=gurchetansingh@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbates@chromium.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.