From: Alyssa Ross <hi@alyssa.is>
To: Gurchetan Singh <gurchetansingh@chromium.org>, qemu-devel@nongnu.org
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: Re: [PATCH v2 0/9] gfxstream + rutabaga_gfx
Date: Tue, 01 Aug 2023 15:00:55 +0000 [thread overview]
Message-ID: <87a5vabye0.fsf@alyssa.is> (raw)
In-Reply-To: <20230801011723.627-1-gurchetansingh@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 171 bytes --]
I was able to replicate my existing crosvm cross-domain testing setup
using QEMU, and all worked. I didn't test any other capsets.
Tested-by: Alyssa Ross <hi@alyssa.is>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-08-01 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 1:17 [PATCH v2 0/9] gfxstream + rutabaga_gfx Gurchetan Singh
2023-08-01 1:17 ` [PATCH v2 1/9] virtio: Add shared memory capability Gurchetan Singh
2023-08-01 1:17 ` [PATCH v2 2/9] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-08-01 1:17 ` [PATCH v2 3/9] virtio-gpu: hostmem Gurchetan Singh
2023-08-01 1:17 ` [PATCH v2 4/9] virtio-gpu: blob prep Gurchetan Singh
2023-08-01 1:17 ` [PATCH v2 5/9] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-08-01 1:17 ` [PATCH v2 6/9] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-08-01 15:11 ` Alyssa Ross
2023-08-02 6:20 ` Akihiko Odaki
2023-08-01 1:17 ` [PATCH v2 7/9] gfxstream + rutabaga: meson support Gurchetan Singh
2023-08-02 6:21 ` Akihiko Odaki
2023-08-01 1:17 ` [PATCH v2 8/9] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-08-02 6:22 ` Akihiko Odaki
2023-08-01 1:17 ` [PATCH v2 9/9] docs/system: add basic virtio-gpu documentation Gurchetan Singh
2023-08-01 15:04 ` Alyssa Ross
2023-08-02 6:37 ` Akihiko Odaki
2023-08-01 15:00 ` Alyssa Ross [this message]
2023-08-02 7:08 ` [PATCH v2 0/9] gfxstream + rutabaga_gfx Akihiko Odaki
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=87a5vabye0.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.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 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.