qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gurchetan Singh <gurchetansingh@chromium.org>
To: qemu-devel@nongnu.org
Cc: --cc=kraxel@redhat.com, marcandre.lureau@redhat.com,
	akihiko.odaki@gmail.com, dmitry.osipenko@collabora.com,
	ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com
Subject: [PATCH v1 0/9] gfxstream + rutabaga_gfx
Date: Mon, 10 Jul 2023 19:56:40 -0700	[thread overview]
Message-ID: <20230711025649.708-1-gurchetansingh@chromium.org> (raw)

From: Gurchetan Singh <gurchetansingh@google.com>

Latest iteration of rutabaga_gfx + gfxstream patches.  Previous version
and more background available here:

https://patchew.org/QEMU/20230421011223.718-1-gurchetansingh@chromium.org/

Changes since RFC:
- All important memory tests pass
- Went with separate virtio-gpu-rutabaga device as suggested by Bernard
  Berschow
- Incorporated review feedback, mostly from Akihiko Odaki
- gfxstream has new unified guest/host repo + build system improvements
- added documentation on virtio-gpu
- new instructions on how to build available in the tracking bug [a]

In terms of API stability/versioning/packaging, once this series is
reviewed, the plan is to cut a "gfxstream upstream release branch".  We
will have the same API guarantees as any other QEMU project then, i.e no
breaking API changes for 5 years.

The Android Emulator will build both gfxstream (to get bug fixes fast)
and QEMU8.0+ (due to regulatory requirements) from sources.  So we haven't
created a gfxstream Debian/Ubuntu package since we actually don't need it.
Though, we plan to upload our QEMU8.0+ gfxstream enabled builds somewhere
on AOSP when it's ready.

It's more important for us to be in-tree to reduce technical debt given
this.  Let us know if there are any strong opinions on packaging.

Otherwise, feedback + reviews welcome!

[a] https://gitlab.com/qemu-project/qemu/-/issues/1611

Antonio Caggiano (2):
  virtio-gpu: CONTEXT_INIT feature
  virtio-gpu: blob prep

Dr. David Alan Gilbert (1):
  virtio: Add shared memory capability

Gerd Hoffmann (1):
  virtio-gpu: hostmem

Gurchetan Singh (5):
  gfxstream + rutabaga prep: added need defintions, fields, and options
  gfxstream + rutabaga: add initial support for gfxstream
  gfxstream + rutabaga: meson support
  gfxstream + rutabaga: enable rutabaga
  docs/system: add basic virtio-gpu documentation

 docs/system/device-emulation.rst     |    1 +
 docs/system/devices/virtio-gpu.rst   |   80 ++
 hw/display/meson.build               |   22 +
 hw/display/virtio-gpu-base.c         |    6 +-
 hw/display/virtio-gpu-pci-rutabaga.c |   48 ++
 hw/display/virtio-gpu-pci.c          |   14 +
 hw/display/virtio-gpu-rutabaga.c     | 1088 ++++++++++++++++++++++++++
 hw/display/virtio-gpu.c              |   17 +-
 hw/display/virtio-vga-rutabaga.c     |   52 ++
 hw/display/virtio-vga.c              |   33 +-
 hw/virtio/virtio-pci.c               |   18 +
 include/hw/virtio/virtio-gpu-bswap.h |   18 +
 include/hw/virtio/virtio-gpu.h       |   34 +
 include/hw/virtio/virtio-pci.h       |    4 +
 meson.build                          |    7 +
 meson_options.txt                    |    2 +
 scripts/meson-buildoptions.sh        |    3 +
 softmmu/qdev-monitor.c               |    3 +
 softmmu/vl.c                         |    1 +
 19 files changed, 1431 insertions(+), 20 deletions(-)
 create mode 100644 docs/system/devices/virtio-gpu.rst
 create mode 100644 hw/display/virtio-gpu-pci-rutabaga.c
 create mode 100644 hw/display/virtio-gpu-rutabaga.c
 create mode 100644 hw/display/virtio-vga-rutabaga.c

-- 
2.41.0.255.g8b1d071c50-goog



             reply	other threads:[~2023-07-11  2:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  2:56 Gurchetan Singh [this message]
2023-07-11  2:56 ` [PATCH v1 1/9] virtio: Add shared memory capability Gurchetan Singh
2023-07-11  2:56 ` [PATCH v1 2/9] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-07-11  2:56 ` [PATCH v1 3/9] virtio-gpu: hostmem Gurchetan Singh
2023-07-11  2:56 ` [PATCH v1 4/9] virtio-gpu: blob prep Gurchetan Singh
2023-07-11  2:56 ` [PATCH v1 5/9] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-07-12 11:36   ` Akihiko Odaki
2023-07-11  2:56 ` [PATCH v1 6/9] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-07-12 12:31   ` Akihiko Odaki
2023-07-12 19:14   ` Marc-André Lureau
2023-07-13  1:27     ` Gurchetan Singh
2023-07-15 19:58   ` Bernhard Beschow
2023-07-11  2:56 ` [PATCH v1 7/9] gfxstream + rutabaga: meson support Gurchetan Singh
2023-07-11  2:56 ` [PATCH v1 8/9] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-07-11  2:56 ` [PATCH v1 9/9] docs/system: add basic virtio-gpu documentation Gurchetan Singh
2023-07-12 21:40   ` Akihiko Odaki
2023-07-13  1:28     ` Gurchetan Singh
2023-07-24  9:56 ` [PATCH v1 0/9] gfxstream + rutabaga_gfx Alyssa Ross
2023-07-26  1:10   ` Gurchetan Singh
2023-08-01 15:18     ` Rutabaga backwards compatibility Alyssa Ross
2023-08-05  1:19       ` Gurchetan Singh
2023-08-05  8:47         ` Alyssa Ross

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=20230711025649.708-1-gurchetansingh@chromium.org \
    --to=gurchetansingh@chromium.org \
    --cc=--cc=kraxel@redhat.com \
    --cc=akihiko.odaki@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=dmitry.osipenko@collabora.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ray.huang@amd.com \
    --cc=shentey@gmail.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;
as well as URLs for NNTP newsgroup(s).