qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, "David Hildenbrand" <david@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/8] virtio-gpu/next - misc fixes and MR handling
Date: Mon, 17 Nov 2025 09:32:26 +0000	[thread overview]
Message-ID: <874iqtm2c5.fsf@draig.linaro.org> (raw)
In-Reply-To: <b3d94838-8484-457e-ada4-8ed3c5b38f8a@tls.msk.ru> (Michael Tokarev's message of "Mon, 17 Nov 2025 11:47:29 +0300")

Michael Tokarev <mjt@tls.msk.ru> writes:

> Hi!
>
> 2 changes from this series has been applied to the master branch:
>
>  9f714c4b20 hw/display: add blob map/unmap trace events
>  0c6d6d79a5 ui/gtk-gl-area: Remove extra draw call in refresh
>
> but the rest weren't.  And it looks like some are worth to be
> considered at least.
>
> Alex, maybe you can refresh the series and re-send?
> We're entering feature freeze stage with 10.2..

There were problems with the other patches leading to leaks in
MemoryRegions. Akihiko has been looking at alternatives patches to
re-factor MemoryRegion handling and also investigating the sub-optimal
RCU behaviour that causes the test case (patch 8) to lock up on the
current master.

Longer term I wonder if there is a better backend we can use that avoids
the need for the complex blob/MemoryRegion dance we currently do between
threads?

>
> Thanks,
>
> /mjt
>
> On 10/14/25 14:12, Alex Bennée wrote:
>> I still have a number of patches that addressed a lock-up but were
>> never merged due to objections. However there is a bunch of discussion
>> around re-factoring the MemoryRegion code so I'm re-posting with an
>> additional functional test which demonstrates the lock-up is fixed.
>> Whatever the final solution for more cleanly handling the binding
>> between MemoryRegions and blobs it will at least need to pass the
>> test.
>> Blob memory issues aside I'll send a PR next week to merge the
>> per-head and ui/gtk-gl-area changes.
>> Discuss,
>> Alex.
>> Alex Bennée (4):
>>    system/memory: add memory_region_finalize tracepoint
>>    hw/display: add blob map/unmap trace events
>>    hw/display: re-arrange memory region tracking
>>    tests/functional: add GPU blob allocation test
>> Andrew Keesler (1):
>>    Support per-head resolutions with virtio-gpu
>> Dongwon Kim (1):
>>    ui/gtk-gl-area: Remove extra draw call in refresh
>> Manos Pitsidianakis (2):
>>    virtio-gpu: refactor async blob unmapping
>>    virtio-gpu: fix hang under TCG when unmapping blob
>>   qapi/virtio.json                          | 10 +++-
>>   include/system/memory.h                   |  1 +
>>   hw/display/virtio-gpu-base.c              | 10 ++++
>>   hw/display/virtio-gpu-virgl.c             | 62 +++++++++++--------
>>   system/memory.c                           |  5 ++
>>   ui/gtk-gl-area.c                          |  1 -
>>   hw/display/trace-events                   |  2 +
>>   system/trace-events                       |  1 +
>>   tests/functional/aarch64/meson.build      |  1 +
>>   tests/functional/aarch64/test_gpu_blob.py | 73 +++++++++++++++++++++++
>>   10 files changed, 138 insertions(+), 28 deletions(-)
>>   create mode 100755 tests/functional/aarch64/test_gpu_blob.py
>> 

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-11-17  9:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 11:12 [PATCH 0/8] virtio-gpu/next - misc fixes and MR handling Alex Bennée
2025-10-14 11:12 ` [PATCH 1/8] Support per-head resolutions with virtio-gpu Alex Bennée
2025-10-15  2:49   ` Akihiko Odaki
2025-10-15  9:40     ` Alex Bennée
2025-10-14 11:12 ` [PATCH 2/8] system/memory: add memory_region_finalize tracepoint Alex Bennée
2025-10-15  3:37   ` Akihiko Odaki
2025-10-14 11:12 ` [PATCH 3/8] ui/gtk-gl-area: Remove extra draw call in refresh Alex Bennée
2025-10-15  3:08   ` Akihiko Odaki
2025-10-15 10:45     ` Alex Bennée
2025-10-15 11:58       ` Akihiko Odaki
2025-10-14 11:12 ` [PATCH 4/8] hw/display: add blob map/unmap trace events Alex Bennée
2025-10-15  3:39   ` Akihiko Odaki
2025-10-14 11:12 ` [PATCH 5/8] hw/display: re-arrange memory region tracking Alex Bennée
2025-10-14 17:00   ` Peter Xu
2025-10-14 11:12 ` [PATCH 6/8] virtio-gpu: refactor async blob unmapping Alex Bennée
2025-10-14 11:12 ` [PATCH 7/8] virtio-gpu: fix hang under TCG when unmapping blob Alex Bennée
2025-10-14 11:12 ` [PATCH 8/8] tests/functional: add GPU blob allocation test Alex Bennée
2025-10-15  2:41   ` Akihiko Odaki
2025-10-15 12:12     ` Akihiko Odaki
2025-11-17  8:47 ` [PATCH 0/8] virtio-gpu/next - misc fixes and MR handling Michael Tokarev
2025-11-17  9:32   ` Alex Bennée [this message]
2025-11-17 11:36     ` 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=874iqtm2c5.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=david@redhat.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=eblake@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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).