From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 98AA1C001E0 for ; Thu, 10 Aug 2023 01:12:53 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qTuDX-0007vH-Oz; Wed, 09 Aug 2023 21:11:59 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qTuDV-0007v3-Mv for qemu-devel@nongnu.org; Wed, 09 Aug 2023 21:11:57 -0400 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qTuDS-0005tr-Rf for qemu-devel@nongnu.org; Wed, 09 Aug 2023 21:11:57 -0400 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-99c4923195dso57767066b.2 for ; Wed, 09 Aug 2023 18:11:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1691629912; x=1692234712; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5RxMy8PsR9fc2oJLgAryuDLJP6xWhn/N/jFi9ixtFOY=; b=nUstRb/IGe+9/V9+v+UHi5QJbWm6UpI75mtIFORLQVh42FD9ygsu7LWwQ0QHxazEAK 3CUfLy82VvZUoeYpxz6iY2x3CX6F9LEILVMz5bDUXabw0lLuQuHPuclzzRNR2JiSa47m HTwuPPx6LNY8nQ7wNTIFyGr7UQQUIEhxroSlI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691629912; x=1692234712; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5RxMy8PsR9fc2oJLgAryuDLJP6xWhn/N/jFi9ixtFOY=; b=Srxwkg909pGf2RJ4469Vehlxr3LANsWAwJG1vsVMOrzw1ZWqzO/PNx+ayDvBAY18we V+7ekPQ6E9hUcFYIWML+zl+Ts/nUSKYrTQOi78nheWR57blwDGEcrPStgKNOC8zLnYz8 ZSLLz622azJPhikP60Dl+IaGvKKO2bUN22QCGannxsQLk+r68NEmLHz2vwHwNWX+iAWY 7k4plKupgbjZvkEikDC6u1yQeRUSuzB7UrCPjwlH66omt3SFcTBLgPb00mqxIdc6l6zt w4GT8ZLM8LLVbyqZRW2YVl9aeI2J2UJIMPiUHhiVQSF97zEywx/T/ipab01O/FdgTXHG mvAQ== X-Gm-Message-State: AOJu0YxA1i5Y2AZsgVerlkJuG7mDm0vlx79/RSjsZkBotiq5EHJoGMi6 8O1pOR9yEZin5Dl2uk7YJ0M8ldtRmd/08fZ/QSgI5w== X-Google-Smtp-Source: AGHT+IFFfHU82OXH9h3b6ysObBdrjunGiJZxTJYD8TmeqkvohP1kwL046oeBG7Q706b4xIjYTDBVrA== X-Received: by 2002:a17:907:2c4d:b0:99d:626f:add with SMTP id hf13-20020a1709072c4d00b0099d626f0addmr606409ejc.24.1691629911872; Wed, 09 Aug 2023 18:11:51 -0700 (PDT) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com. [209.85.208.53]) by smtp.gmail.com with ESMTPSA id v9-20020a170906338900b00992b1c93279sm211475eja.110.2023.08.09.18.11.51 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Aug 2023 18:11:51 -0700 (PDT) Received: by mail-ed1-f53.google.com with SMTP id 4fb4d7f45d1cf-5232ce75e26so2951a12.1 for ; Wed, 09 Aug 2023 18:11:51 -0700 (PDT) X-Received: by 2002:a50:d549:0:b0:519:7d2:e256 with SMTP id f9-20020a50d549000000b0051907d2e256mr177254edj.0.1691629911152; Wed, 09 Aug 2023 18:11:51 -0700 (PDT) MIME-Version: 1.0 References: <20230809021108.674-1-gurchetansingh@chromium.org> <20230809021108.674-10-gurchetansingh@chromium.org> <41d8c647-164a-46ce-aaee-f48bc5f4d752@gmail.com> In-Reply-To: <41d8c647-164a-46ce-aaee-f48bc5f4d752@gmail.com> From: Gurchetan Singh Date: Wed, 9 Aug 2023 18:11:39 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 9/9] docs/system: add basic virtio-gpu documentation To: Akihiko Odaki Cc: qemu-devel@nongnu.org, marcandre.lureau@redhat.com, kraxel@redhat.com, ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com, hi@alyssa.is, ernunes@redhat.com Content-Type: multipart/alternative; boundary="000000000000f2bad306028747fa" Received-SPF: pass client-ip=2a00:1450:4864:20::630; envelope-from=gurchetansingh@chromium.org; helo=mail-ej1-x630.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org --000000000000f2bad306028747fa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 8, 2023 at 10:18=E2=80=AFPM Akihiko Odaki wrote: > On 2023/08/09 11:11, Gurchetan Singh wrote: > > This adds basic documentation for virtio-gpu. > > > > Suggested-by: Akihiko Odaki > > Signed-off-by: Gurchetan Singh > > --- > > v2: - Incorporated suggestions by Akihiko Odaki > > - Listed the currently supported capset_names (Bernard) > > > > v3: - Incorporated suggestions by Akihiko Odaki and Alyssa Ross > > > > v4: - Incorporated suggestions by Akihiko Odaki > > > > docs/system/device-emulation.rst | 1 + > > docs/system/devices/virtio-gpu.rst | 115 ++++++++++++++++++++++++++++= + > > 2 files changed, 116 insertions(+) > > create mode 100644 docs/system/devices/virtio-gpu.rst > > > > diff --git a/docs/system/device-emulation.rst > b/docs/system/device-emulation.rst > > index 4491c4cbf7..1167f3a9f2 100644 > > --- a/docs/system/device-emulation.rst > > +++ b/docs/system/device-emulation.rst > > @@ -91,6 +91,7 @@ Emulated Devices > > devices/nvme.rst > > devices/usb.rst > > devices/vhost-user.rst > > + devices/virtio-gpu.rst > > devices/virtio-pmem.rst > > devices/vhost-user-rng.rst > > devices/canokey.rst > > diff --git a/docs/system/devices/virtio-gpu.rst > b/docs/system/devices/virtio-gpu.rst > > new file mode 100644 > > index 0000000000..d56524270d > > --- /dev/null > > +++ b/docs/system/devices/virtio-gpu.rst > > @@ -0,0 +1,115 @@ > > +.. > > + SPDX-License-Identifier: GPL-2.0 > > + > > +virtio-gpu > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > + > > +This document explains the setup and usage of the virtio-gpu device. > > +The virtio-gpu device paravirtualizes the GPU and display controller. > > + > > +Linux kernel support > > +-------------------- > > + > > +virtio-gpu requires a guest Linux kernel built with the > > +``CONFIG_DRM_VIRTIO_GPU`` option. > > + > > +QEMU virtio-gpu variants > > +------------------------ > > + > > +QEMU virtio-gpu device variants come in the following form: > > + > > + * ``virtio-vga[-BACKEND]`` > > + * ``virtio-gpu[-BACKEND][-INTERFACE]`` > > + * ``vhost-user-vga`` > > + * ``vhost-user-pci`` > > + > > +**Backends:** QEMU provides a 2D virtio-gpu backend, and two accelerat= ed > > +backends: virglrenderer ('gl' device label) and rutabaga_gfx ('rutabag= a' > > +device label). There is a vhost-user backend that runs the graphics > stack > > +in a separate process for improved isolation. > > + > > +**Interfaces:** QEMU further categorizes virtio-gpu device variants > based > > +on the interface exposed to the guest. The interfaces can be classifie= d > > +into VGA and non-VGA variants. The VGA ones are prefixed with virtio-v= ga > > +or vhost-user-vga while the non-VGA ones are prefixed with virtio-gpu = or > > +vhost-user-gpu. > > + > > +The VGA ones always use the PCI interface, but for the non-VGA ones, t= he > > +user can further pick between MMIO or PCI. For MMIO, the user can suff= ix > > +the device name with -device, though vhost-user-gpu does not support > MMIO. > > +For PCI, the user can suffix it with -pci. Without these suffixes, the > > +platform default will be chosen. > > + > > +This document uses the PCI interface in examples. > > I think it's better to omit -pci. > Are you suggesting to use "-device virtio-gpu-rutabaga" or "-device virtio-gpu-gl" in the examples? Or "-device virtio-gpu-rutabaga-device" or "-device virtio-gpu-gl-device"? The former I believe wouldn't launch, and the examples should ideally be directly applicable to a user. > > By the way you are not adding the aliases for Rutabaga so please do so. > You can find the table in: softmmu/qdev-monitor.c > I don't follow this comment. Isn't "-device virtio-gpu-rutabaga-pci" (along with "-device virtio-gpu-rutabaga-device") an alias for the rutabaga device? Where would the alias be placed in the doc (we don't explicitly list aliases for other devices either), outside the "..parsed-literal::" launch command? > > > + > > +virtio-gpu 2d > > +------------- > > + > > +The default 2D backend only performs 2D operations. The guest needs to > > +employ a software renderer for 3D graphics. > > + > > +Typically, the software renderer is provided by `Mesa`_ or > `SwiftShader`_. > > +Mesa's implementations (LLVMpipe, Lavapipe and virgl below) work out o= f > box > > +on typical modern Linux distributions. > > + > > +.. parsed-literal:: > > + -device virtio-gpu-pci > > + > > +.. _Mesa: https://www.mesa3d.org/ > > +.. _SwiftShader: https://github.com/google/swiftshader > > + > > +virtio-gpu virglrenderer > > +------------------------ > > + > > +When using virgl accelerated graphics mode in the guest, OpenGL API > calls > > +are translated into an intermediate representation (see `Gallium3D`_). > The > > +intermediate representation is communicated to the host and the > > +`virglrenderer`_ library on the host translates the intermediate > > +representation back to OpenGL API calls. > > + > > +.. parsed-literal:: > > + -device virtio-gpu-gl-pci > > + > > +.. _Gallium3D: https://www.freedesktop.org/wiki/Software/gallium/ > > +.. _virglrenderer: https://gitlab.freedesktop.org/virgl/virglrenderer/ > > + > > +virtio-gpu rutabaga > > +------------------- > > + > > +virtio-gpu can also leverage `rutabaga_gfx`_ to provide `gfxstream`_ > > +rendering and `Wayland display passthrough`_. With the gfxstream > rendering > > +mode, GLES and Vulkan calls are forwarded to the host with minimal > > +modification. > > + > > +The crosvm book provides directions on how to build a `gfxstream-enabl= ed > > +rutabaga`_ and launch a `guest Wayland proxy`_. > > + > > +This device does require host blob support (``hostmem`` field below). > The > > +``hostmem`` field specifies the size of virtio-gpu host memory window. > > +This is typically between 256M and 8G. > > + > > +At least one capset (see colon separated ``capset_names`` below) must = be > > +specified when starting the device. The currently supported > > +``capset_names`` are ``gfxstream-vulkan`` and ``cross-domain`` on Linu= x > > +guests. For Android guests, ``gfxstream-gles`` is also supported. > > + > > +The device will try to auto-detect the wayland socket path if the > > +``cross-domain`` capset name is set. The user may optionally specify > > +``wayland_socket_path`` for non-standard paths. > > + > > +The ``wsi`` option can be set to ``surfaceless`` or ``headless``. > > +Surfaceless doesn't create a native window surface, but does copy from > the > > +render target to the Pixman buffer if a virtio-gpu 2D hypercall is > issued. > > +Headless is like surfaceless, but doesn't copy to the Pixman buffer. > > +Surfaceless is the default if ``wsi`` is not specified. > > + > > +.. parsed-literal:: > > + -device > virtio-gpu-rutabaga-pci,capset_names=3Dgfxstream-vulkan:cross-domain, > > + > hostmem=3D8G,wayland_socket_path=3D/tmp/nonstandard/mock_wayland.sock, > > + wsi=3Dheadless > > + > > +.. _rutabaga_gfx: > https://github.com/google/crosvm/blob/main/rutabaga_gfx/ffi/src/include/r= utabaga_gfx_ffi.h > > +.. _gfxstream: > https://android.googlesource.com/platform/hardware/google/gfxstream/ > > +.. _Wayland display passthrough: > https://www.youtube.com/watch?v=3DOZJiHMtIQ2M > > +.. _gfxstream-enabled rutabaga: > https://crosvm.dev/book/appendix/rutabaga_gfx.html > > The build procedure looks almost good, but a command for building > gfxstream: > meson -Ddefault_library=3Dstatic build/ > > This results in a warning: > WARNING: Running the setup command as `meson [options]` instead of > `meson setup [options]` is ambiguous and deprecated. > > The same goes for the command for guest-side libraries. > > > +.. _guest Wayland proxy: https://crosvm.dev/book/devices/wayland.html > --000000000000f2bad306028747fa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Aug 8, 2023 at 10:18=E2=80=AF= PM Akihiko Odaki <akihiko.oda= ki@gmail.com> wrote:
On 2023/08/09 11:11, Gurchetan Singh wrote:
> This adds basic documentation for virtio-gpu.
>
> Suggested-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
> ---
> v2: - Incorporated suggestions by Akihiko Odaki
>=C2=A0 =C2=A0 =C2=A0 - Listed the currently supported capset_names (Ber= nard)
>
> v3: - Incorporated suggestions by Akihiko Odaki and Alyssa Ross
>
> v4: - Incorporated suggestions by Akihiko Odaki
>
>=C2=A0 =C2=A0docs/system/device-emulation.rst=C2=A0 =C2=A0|=C2=A0 =C2= =A01 +
>=C2=A0 =C2=A0docs/system/devices/virtio-gpu.rst | 115 +++++++++++++++++= ++++++++++++
>=C2=A0 =C2=A02 files changed, 116 insertions(+)
>=C2=A0 =C2=A0create mode 100644 docs/system/devices/virtio-gpu.rst
>
> diff --git a/docs/system/device-emulation.rst b/docs/system/device-emu= lation.rst
> index 4491c4cbf7..1167f3a9f2 100644
> --- a/docs/system/device-emulation.rst
> +++ b/docs/system/device-emulation.rst
> @@ -91,6 +91,7 @@ Emulated Devices
>=C2=A0 =C2=A0 =C2=A0 devices/nvme.rst
>=C2=A0 =C2=A0 =C2=A0 devices/usb.rst
>=C2=A0 =C2=A0 =C2=A0 devices/vhost-user.rst
> +=C2=A0 =C2=A0devices/virtio-gpu.rst
>=C2=A0 =C2=A0 =C2=A0 devices/virtio-pmem.rst
>=C2=A0 =C2=A0 =C2=A0 devices/vhost-user-rng.rst
>=C2=A0 =C2=A0 =C2=A0 devices/canokey.rst
> diff --git a/docs/system/devices/virtio-gpu.rst b/docs/system/devices/= virtio-gpu.rst
> new file mode 100644
> index 0000000000..d56524270d
> --- /dev/null
> +++ b/docs/system/devices/virtio-gpu.rst
> @@ -0,0 +1,115 @@
> +..
> +=C2=A0 =C2=A0SPDX-License-Identifier: GPL-2.0
> +
> +virtio-gpu
> +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> +
> +This document explains the setup and usage of the virtio-gpu device.<= br> > +The virtio-gpu device paravirtualizes the GPU and display controller.=
> +
> +Linux kernel support
> +--------------------
> +
> +virtio-gpu requires a guest Linux kernel built with the
> +``CONFIG_DRM_VIRTIO_GPU`` option.
> +
> +QEMU virtio-gpu variants
> +------------------------
> +
> +QEMU virtio-gpu device variants come in the following form:
> +
> + * ``virtio-vga[-BACKEND]``
> + * ``virtio-gpu[-BACKEND][-INTERFACE]``
> + * ``vhost-user-vga``
> + * ``vhost-user-pci``
> +
> +**Backends:** QEMU provides a 2D virtio-gpu backend, and two accelera= ted
> +backends: virglrenderer ('gl' device label) and rutabaga_gfx = ('rutabaga'
> +device label).=C2=A0 There is a vhost-user backend that runs the grap= hics stack
> +in a separate process for improved isolation.
> +
> +**Interfaces:** QEMU further categorizes virtio-gpu device variants b= ased
> +on the interface exposed to the guest. The interfaces can be classifi= ed
> +into VGA and non-VGA variants. The VGA ones are prefixed with virtio-= vga
> +or vhost-user-vga while the non-VGA ones are prefixed with virtio-gpu= or
> +vhost-user-gpu.
> +
> +The VGA ones always use the PCI interface, but for the non-VGA ones, = the
> +user can further pick between MMIO or PCI. For MMIO, the user can suf= fix
> +the device name with -device, though vhost-user-gpu does not support = MMIO.
> +For PCI, the user can suffix it with -pci. Without these suffixes, th= e
> +platform default will be chosen.
> +
> +This document uses the PCI interface in examples.

I think it's better to omit -pci.

A= re you suggesting to use "-device virtio-gpu-rutabaga" or "-= device virtio-gpu-gl" in the examples?=C2=A0 Or "-device virtio-g= pu-rutabaga-device" or "-device virtio-gpu-gl-device"?=C2=A0= The former I believe wouldn't launch, and the examples should ideally = be directly applicable to a user.=C2=A0
=C2=A0

By the way you are not adding the aliases for Rutabaga so please do so. You can find the table in: softmmu/qdev-monitor.c

=
I don't follow this comment.=C2=A0 Isn't "-device v= irtio-gpu-rutabaga-pci" (along with "-device virtio-gpu-rutabaga-= device") an alias for the rutabaga device?=C2=A0 Where would the alias= be placed in the doc (we don't explicitly list aliases for other devic= es either), outside the "..parsed-literal::" launch command?
=C2=A0

> +
> +virtio-gpu 2d
> +-------------
> +
> +The default 2D backend only performs 2D operations. The guest needs t= o
> +employ a software renderer for 3D graphics.
> +
> +Typically, the software renderer is provided by `Mesa`_ or `SwiftShad= er`_.
> +Mesa's implementations (LLVMpipe, Lavapipe and virgl below) work = out of box
> +on typical modern Linux distributions.
> +
> +.. parsed-literal::
> +=C2=A0 =C2=A0 -device virtio-gpu-pci
> +
> +.. _Mesa: https://www.mesa3d.org/
> +.. _SwiftShader: https://github.com/google/swiftshader
> +
> +virtio-gpu virglrenderer
> +------------------------
> +
> +When using virgl accelerated graphics mode in the guest, OpenGL API c= alls
> +are translated into an intermediate representation (see `Gallium3D`_)= . The
> +intermediate representation is communicated to the host and the
> +`virglrenderer`_ library on the host translates the intermediate
> +representation back to OpenGL API calls.
> +
> +.. parsed-literal::
> +=C2=A0 =C2=A0 -device virtio-gpu-gl-pci
> +
> +.. _Gallium3D: https://www.freedesktop.org/w= iki/Software/gallium/
> +.. _virglrenderer: https://gitlab.freedeskt= op.org/virgl/virglrenderer/
> +
> +virtio-gpu rutabaga
> +-------------------
> +
> +virtio-gpu can also leverage `rutabaga_gfx`_ to provide `gfxstream`_<= br> > +rendering and `Wayland display passthrough`_.=C2=A0 With the gfxstrea= m rendering
> +mode, GLES and Vulkan calls are forwarded to the host with minimal > +modification.
> +
> +The crosvm book provides directions on how to build a `gfxstream-enab= led
> +rutabaga`_ and launch a `guest Wayland proxy`_.
> +
> +This device does require host blob support (``hostmem`` field below).= The
> +``hostmem`` field specifies the size of virtio-gpu host memory window= .
> +This is typically between 256M and 8G.
> +
> +At least one capset (see colon separated ``capset_names`` below) must= be
> +specified when starting the device.=C2=A0 The currently supported
> +``capset_names`` are ``gfxstream-vulkan`` and ``cross-domain`` on Lin= ux
> +guests. For Android guests, ``gfxstream-gles`` is also supported.
> +
> +The device will try to auto-detect the wayland socket path if the
> +``cross-domain`` capset name is set.=C2=A0 The user may optionally sp= ecify
> +``wayland_socket_path`` for non-standard paths.
> +
> +The ``wsi`` option can be set to ``surfaceless`` or ``headless``.
> +Surfaceless doesn't create a native window surface, but does copy= from the
> +render target to the Pixman buffer if a virtio-gpu 2D hypercall is is= sued.
> +Headless is like surfaceless, but doesn't copy to the Pixman buff= er.
> +Surfaceless is the default if ``wsi`` is not specified.
> +
> +.. parsed-literal::
> +=C2=A0 =C2=A0 -device virtio-gpu-rutabaga-pci,capset_names=3Dgfxstrea= m-vulkan:cross-domain,
> +=C2=A0 =C2=A0 =C2=A0 =C2=A0hostmem=3D8G,wayland_socket_path=3D/tmp/no= nstandard/mock_wayland.sock,
> +=C2=A0 =C2=A0 =C2=A0 =C2=A0wsi=3Dheadless
> +
> +.. _rutabaga_gfx: https://github.com/google/crosvm/blob/main/rutabaga_gfx/ffi/s= rc/include/rutabaga_gfx_ffi.h
> +.. _gfxstream: https://and= roid.googlesource.com/platform/hardware/google/gfxstream/
> +.. _Wayland display passthrough: https://www.yout= ube.com/watch?v=3DOZJiHMtIQ2M
> +.. _gfxstream-enabled rutabaga: https://cros= vm.dev/book/appendix/rutabaga_gfx.html

The build procedure looks almost good, but a command for building gfxstream= :
meson -Ddefault_library=3Dstatic build/

This results in a warning:
WARNING: Running the setup command as `meson [options]` instead of
`meson setup [options]` is ambiguous and deprecated.

The same goes for the command for guest-side libraries.

> +.. _guest Wayland proxy: https://crosvm.dev/book/d= evices/wayland.html
--000000000000f2bad306028747fa--