From: Gurchetan Singh <gurchetansingh@chromium.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org, philmd@linaro.org, kraxel@redhat.com,
akihiko.odaki@gmail.com, dmitry.osipenko@collabora.com,
ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com
Subject: Re: [PATCH v3 0/5] virtio-gpu cleanups and obvious definitions
Date: Tue, 9 May 2023 10:53:10 -0700 [thread overview]
Message-ID: <CAAfnVBnakdA+q=+GDv0gFxFrQHTutsw=C=rPYm8vSSsNwhg1ag@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1CK+myw2n3bvT9Ys-heDr8W-CatJcroR=cPOpJUv_VDNwQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]
On Tue, May 9, 2023 at 5:43 AM Marc-André Lureau <marcandre.lureau@gmail.com>
wrote:
> Hi
>
> On Thu, May 4, 2023 at 11:13 PM Gurchetan Singh <
> gurchetansingh@chromium.org> wrote:
>
>> From: Gurchetan Singh <gurchetansingh@google.com>
>>
>> v3 of "virtio-gpu cleanups and obvious definitions"
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2023-04/msg05392.html
>>
>> All patches have been reviewed, though there was a question from
>> Bernhard Beschow about patch (3) and how it fits with the QOM:
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg00057.html
>>
>> I go into detail in patch 3 commit message, but I think we meet
>> the requirements (which are tricky/fuzzy anyways). Also, I think
>> this is the cleanest way to add another 3D virtgpu backend. But
>> if anyone has other ideas, please do reply/review.
>>
>> Antonio Caggiano (1):
>> virtio-gpu: CONTEXT_INIT feature
>>
>> Dr. David Alan Gilbert (1):
>> virtio: Add shared memory capability
>>
>> Gurchetan Singh (3):
>> hw/display/virtio-gpu-virgl: virtio_gpu_gl -> virtio_gpu_virgl
>> hw/display/virtio-gpu-virgl: make GL device more library agnostic
>> hw/display/virtio-gpu-virgl: define callbacks in realize function
>>
>> hw/display/virtio-gpu-base.c | 3 +
>> hw/display/virtio-gpu-gl.c | 114 +--------------------------
>> hw/display/virtio-gpu-virgl.c | 137 +++++++++++++++++++++++++++++++--
>> hw/virtio/virtio-pci.c | 18 +++++
>> include/hw/virtio/virtio-gpu.h | 11 +--
>> include/hw/virtio/virtio-pci.h | 4 +
>> 6 files changed, 160 insertions(+), 127 deletions(-)
>>
>> --
>> 2.40.1.521.gf1e218fcd8-goog
>>
>>
>>
> This looks fine to me:
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> however, do you have a series rebased on top that makes use of those
> changes? (I think we may want to delay merging this one until it's actually
> needed)
>
Got it. Bernhard actually recommended a separate virtio-gpu-rutabaga
device instead of virtio-gpu-gl. I went with that approach:
https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg01571.html
https://gitlab.freedesktop.org/gurchetansingh/qemu-gfxstream/-/commits/qemu-gfxstream-3
I'll send out a new full-featured series once testing/hack cleanups are
complete -- so no further action is needed on your part.
>
>
> --
> Marc-André Lureau
>
[-- Attachment #2: Type: text/html, Size: 4038 bytes --]
prev parent reply other threads:[~2023-05-09 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 19:12 [PATCH v3 0/5] virtio-gpu cleanups and obvious definitions Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 1/5] hw/display/virtio-gpu-virgl: virtio_gpu_gl -> virtio_gpu_virgl Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 2/5] hw/display/virtio-gpu-virgl: make GL device more library agnostic Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 3/5] hw/display/virtio-gpu-virgl: define callbacks in realize function Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 4/5] virtio: Add shared memory capability Gurchetan Singh
2023-05-04 19:12 ` [PATCH v3 5/5] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-05-05 4:56 ` [PATCH v3 0/5] virtio-gpu cleanups and obvious definitions Akihiko Odaki
2023-05-09 12:43 ` Marc-André Lureau
2023-05-09 17:53 ` Gurchetan Singh [this message]
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='CAAfnVBnakdA+q=+GDv0gFxFrQHTutsw=C=rPYm8vSSsNwhg1ag@mail.gmail.com' \
--to=gurchetansingh@chromium.org \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=philmd@linaro.org \
--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).