From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
"Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Huang Rui" <ray.huang@amd.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gert Wollny" <gert.wollny@collabora.com>,
qemu-devel@nongnu.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Alyssa Ross" <hi@alyssa.is>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Stefano Stabellini" <stefano.stabellini@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Xenia Ragiadakou" <xenia.ragiadakou@amd.com>,
"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
"Honglei Huang" <honglei1.huang@amd.com>,
"Julia Zhang" <julia.zhang@amd.com>,
"Chen Jiqian" <Jiqian.Chen@amd.com>,
"Rob Clark" <robdclark@gmail.com>,
"Yiwei Zhang" <zzyiwei@chromium.org>,
"Sergio Lopez Pascual" <slp@redhat.com>
Subject: Re: [PATCH v2 0/6] Support virtio-gpu DRM native context
Date: Thu, 24 Oct 2024 13:45:27 +0100 [thread overview]
Message-ID: <87v7xhis9k.fsf@draig.linaro.org> (raw)
In-Reply-To: <999ae767-41ab-49aa-a3b6-bbe2d63164d8@collabora.com> (Dmitry Osipenko's message of "Thu, 24 Oct 2024 15:21:05 +0300")
Dmitry Osipenko <dmitry.osipenko@collabora.com> writes:
> On 10/24/24 13:09, Alex Bennée wrote:
>> Dmitry Osipenko <dmitry.osipenko@collabora.com> writes:
>>
>>> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>>> It's based on the pending Venus v17 patches [1] that bring host blobs
>>> support to virtio-gpu-gl device.
>>>
>>> Based-on: 20240822185110.1757429-1-dmitry.osipenko@collabora.com
>>>
>>> [1]
>>> https://lore.kernel.org/qemu-devel/20240822185110.1757429-1-dmitry.osipenko@collabora.com/
>>
>> Now the tree is open are you going to re-base with the tags and get it
>> merged? We don't have long before softfreeze for 9.2!
>
> The Venus patches apply cleanly to the latest base. I'll re-send them
> today in a hope that it will speed up the merging process. Thanks for
> the heads up.
>
> Patches should be waiting for Michael Tsirkin to press a button to get
> them merged. On the other hand, I now see MAINTAINERS says that
> virtio-gpu status is "Orphan", thought Michael/Gerd are in charge of it.
> Does it means that any QEMU maintainer with a commit access could help
> with applying virtio-gpu patches?
In theory although it would be better if we could find someone to
step-up to maintainer duties. Could that be you?
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-10-24 12:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 4:32 [PATCH v2 0/6] Support virtio-gpu DRM native context Dmitry Osipenko
2024-10-15 4:32 ` [PATCH v2 1/6] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2024-10-15 4:32 ` [PATCH v2 2/6] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2024-10-18 5:22 ` Akihiko Odaki
2024-10-21 1:02 ` Dmitry Osipenko
2024-10-15 4:32 ` [PATCH v2 3/6] linux-headers: Update to Linux v6.12-rc1 Dmitry Osipenko
2024-10-15 4:32 ` [PATCH v2 4/6] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2024-10-15 4:32 ` [PATCH v2 5/6] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
2024-10-18 5:28 ` Akihiko Odaki
2024-10-18 21:31 ` Dmitry Osipenko
2024-10-22 5:11 ` Akihiko Odaki
2024-10-22 12:37 ` Dmitry Osipenko
2024-10-22 12:44 ` Dmitry Osipenko
2024-10-23 7:51 ` Akihiko Odaki
2024-10-23 10:04 ` Akihiko Odaki
2024-10-24 0:09 ` Dmitry Osipenko
2024-10-15 4:32 ` [PATCH v2 6/6] virtio-gpu: Support DRM native context Dmitry Osipenko
2024-10-18 5:33 ` Akihiko Odaki
2024-10-21 1:33 ` Dmitry Osipenko
2024-10-24 10:09 ` [PATCH v2 0/6] Support virtio-gpu " Alex Bennée
2024-10-24 12:21 ` Dmitry Osipenko
2024-10-24 12:45 ` Alex Bennée [this message]
2024-10-24 17:12 ` Dmitry Osipenko
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=87v7xhis9k.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=Jiqian.Chen@amd.com \
--cc=akihiko.odaki@daynix.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gert.wollny@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=hi@alyssa.is \
--cc=honglei1.huang@amd.com \
--cc=julia.zhang@amd.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=robdclark@gmail.com \
--cc=roger.pau@citrix.com \
--cc=slp@redhat.com \
--cc=stefano.stabellini@amd.com \
--cc=xenia.ragiadakou@amd.com \
--cc=zzyiwei@chromium.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).