qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PULL 00/13] virtio-gpu vulkan support
Date: Tue, 29 Oct 2024 12:10:17 +0000	[thread overview]
Message-ID: <20241029121030.4007014-1-alex.bennee@linaro.org> (raw)

The following changes since commit fdf250e5a37830615e324017cb3a503e84b3712c:

  Merge tag 'pull-maintainer-oct-misc-241024-1' of https://gitlab.com/stsquad/qemu into staging (2024-10-25 19:12:06 +0100)

are available in the Git repository at:

  https://gitlab.com/stsquad/qemu.git tags/pull-virtio-gpu-vulkan-291024-1

for you to fetch changes up to 94d0ea1c19289d76ced934711fccd2269e69bb29:

  virtio-gpu: Support Venus context (2024-10-28 16:56:36 +0000)

----------------------------------------------------------------
virtio-gpu: add venus/vulkan capability

We are currently lacking a declared maintainer for the sub-system so
while we look for one I'm merging after testing locally.

  - convert some fprintfs to proper trace events
  - move timers used by GL devices into GL structures
  - handle virtio_gpu_virgl_init() failure better
  - implement unrealize for GL devices
  - use virgl version numbering to gate features
  - support context-init feature
  - don't require udmabuf for virgl only
  - add virgl resource tracker
  - allow command submission to be suspended
  - handle resource blob commands
  - dynamically handle capabilit sets
  - add venus context support for passing vulkan

----------------------------------------------------------------
Antonio Caggiano (1):
      virtio-gpu: Support Venus context

Dmitry Osipenko (8):
      virtio-gpu: Use trace events for tracking number of in-flight fences
      virtio-gpu: Move fence_poll timer to VirtIOGPUGL
      virtio-gpu: Move print_stats timer to VirtIOGPUGL
      virtio-gpu: Handle virtio_gpu_virgl_init() failure
      virtio-gpu: Unrealize GL device
      virtio-gpu: Use pkgconfig version to decide which virgl features are available
      virtio-gpu: Don't require udmabuf when blobs and virgl are enabled
      virtio-gpu: Support suspension of commands processing

Huang Rui (2):
      virtio-gpu: Support context-init feature with virglrenderer
      virtio-gpu: Add virgl resource management

Pierre-Eric Pelloux-Prayer (1):
      virtio-gpu: Register capsets dynamically

Robert Beckett (1):
      virtio-gpu: Handle resource blob commands

 docs/system/devices/virtio-gpu.rst |  11 +
 meson.build                        |   5 +-
 include/hw/virtio/virtio-gpu.h     |  32 +-
 hw/display/virtio-gpu-gl.c         |  62 +++-
 hw/display/virtio-gpu-virgl.c      | 585 +++++++++++++++++++++++++++++++++++--
 hw/display/virtio-gpu.c            |  44 ++-
 hw/display/trace-events            |   3 +
 7 files changed, 685 insertions(+), 57 deletions(-)


-- 
2.39.5



             reply	other threads:[~2024-10-29 12:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 12:10 Alex Bennée [this message]
2024-10-29 12:10 ` [PULL 01/13] virtio-gpu: Use trace events for tracking number of in-flight fences Alex Bennée
2024-10-29 12:10 ` [PULL 02/13] virtio-gpu: Move fence_poll timer to VirtIOGPUGL Alex Bennée
2024-10-29 12:10 ` [PULL 03/13] virtio-gpu: Move print_stats " Alex Bennée
2024-10-29 12:10 ` [PULL 04/13] virtio-gpu: Handle virtio_gpu_virgl_init() failure Alex Bennée
2024-10-29 12:10 ` [PULL 05/13] virtio-gpu: Unrealize GL device Alex Bennée
2024-10-29 12:10 ` [PULL 06/13] virtio-gpu: Use pkgconfig version to decide which virgl features are available Alex Bennée
2024-10-29 12:10 ` [PULL 07/13] virtio-gpu: Support context-init feature with virglrenderer Alex Bennée
2024-10-29 12:10 ` [PULL 08/13] virtio-gpu: Don't require udmabuf when blobs and virgl are enabled Alex Bennée
2024-10-29 12:10 ` [PULL 09/13] virtio-gpu: Add virgl resource management Alex Bennée
2024-10-29 12:10 ` [PULL 10/13] virtio-gpu: Support suspension of commands processing Alex Bennée
2024-10-29 12:10 ` [PULL 11/13] virtio-gpu: Handle resource blob commands Alex Bennée
2024-11-01 15:35   ` Peter Maydell
2024-11-01 16:04     ` Dmitry Osipenko
2024-11-01 17:17       ` Alex Bennée
2024-11-01 17:16     ` Alex Bennée
2024-11-01 18:23       ` Dmitry Osipenko
2024-11-04 11:48         ` Alex Bennée
2024-11-04 13:50           ` BALATON Zoltan
2024-10-29 12:10 ` [PULL 12/13] virtio-gpu: Register capsets dynamically Alex Bennée
2024-10-29 12:10 ` [PULL 13/13] virtio-gpu: Support Venus context Alex Bennée
2024-10-31 11:29 ` [PULL 00/13] virtio-gpu vulkan support Peter Maydell

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=20241029121030.4007014-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).