From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "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>,
"Alex Bennée" <alex.bennee@linaro.org>,
"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 v4 0/5] Support virtio-gpu DRM native context
Date: Sun, 12 Jan 2025 18:48:33 +0300 [thread overview]
Message-ID: <bcc3b08e-751f-4167-9af9-e98da4ee9dc8@collabora.com> (raw)
In-Reply-To: <20250108081322-mutt-send-email-mst@kernel.org>
On 1/8/25 16:14, Michael S. Tsirkin wrote:
> On Mon, Nov 11, 2024 at 01:18:32AM +0300, Dmitry Osipenko wrote:
>> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>>
>> Contarary to Virgl and Venus contexts which mediate high level GFX APIs,
>> DRM native context [1] mediates lower level kernel driver UAPI, which
>> reflects in a less CPU overhead and less/simpler code needed to support it.
>> DRM context consists of a host and guest parts that have to be implemented
>> for each GPU driver. On a guest side, DRM context presents a virtual GPU as
>> a real/native host GPU device for GL/VK applications.
>>
>> [1] https://www.youtube.com/watch?v=9sFP_yddLLQ
>>
>> Today there are four known DRM native context drivers existing in a wild:
>>
>> - Freedreno (Qualcomm SoC GPUs), completely upstreamed
>> - AMDGPU, mostly merged into upstreams
>> - Intel (i915), merge requests are opened
>> - Asahi (Apple SoC GPUs), WIP status
>
> Took a quick look, looks ok
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> Gerd, you gonnu pick this up?
>
> Dmitry, if you will post a rebase, I can apply too.
Thanks! The plan was that Alex will test this patchset on his setup and
then either he or you will apply it. Will post the rebased version too,
there is a minor merge conflict with the latest Qemu tree now.
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-01-12 15:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 22:18 [PATCH v4 0/5] Support virtio-gpu DRM native context Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 1/5] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 2/5] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 3/5] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 4/5] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
2025-01-13 22:00 ` Alex Bennée
2025-01-14 12:19 ` Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 5/5] virtio-gpu: Support DRM native context Dmitry Osipenko
2024-11-11 5:18 ` [PATCH v4 0/5] Support virtio-gpu " Akihiko Odaki
2025-01-08 13:14 ` Michael S. Tsirkin
2025-01-12 15:48 ` Dmitry Osipenko [this message]
2025-01-10 12:16 ` Alex Bennée
2025-01-12 15:49 ` Dmitry Osipenko
2025-01-10 13:38 ` Alex Bennée
2025-01-12 15:56 ` Dmitry Osipenko
2025-01-12 16:14 ` Alex Bennée
2025-01-12 16:46 ` Dmitry Osipenko
2025-01-12 17:05 ` Alex Bennée
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=bcc3b08e-751f-4167-9af9-e98da4ee9dc8@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=Jiqian.Chen@amd.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.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).