From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Alyssa Ross <hi@alyssa.is>
Subject: [PATCH v1 0/3] Fix resource freeing bugs in virtio-gpu-rutabaga
Date: Fri, 26 Jan 2024 16:41:47 +0200 [thread overview]
Message-ID: <cover.1706279540.git.manos.pitsidianakis@linaro.org> (raw)
While testing the rutabaga gpu device, we noticed that if the device is
reset, it stops working and complains about missing resource ids. A
quick investigation discovered that the generic VirtIOGPU implementation
frees all resources, but for Rutabaga, they are tied with rutabaga
objects that need to be destroyed as well.
This series adds a resource_destroy class method that the Rutabaga
device can override and do its own bookkeeping.
Manos Pitsidianakis (3):
hw/display/virtio-gpu.c: use reset_bh class method
virtio-gpu.c: add resource_destroy class method
virtio-gpu-rutabaga.c: override resource_destroy method
hw/display/virtio-gpu-rutabaga.c | 31 ++++++++++++++++++++-----------
hw/display/virtio-gpu.c | 21 +++++++++++++++++----
include/hw/virtio/virtio-gpu.h | 2 ++
3 files changed, 39 insertions(+), 15 deletions(-)
base-commit: e029fe22caad9b75c7ab69bd4e84853c11fb71e0
--
γαῖα πυρί μιχθήτω
next reply other threads:[~2024-01-26 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 14:41 Manos Pitsidianakis [this message]
2024-01-26 14:41 ` [PATCH v1 1/3] hw/display/virtio-gpu.c: use reset_bh class method Manos Pitsidianakis
2024-01-29 8:17 ` Marc-André Lureau
2024-01-26 14:41 ` [PATCH v1 2/3] virtio-gpu.c: add resource_destroy " Manos Pitsidianakis
2024-01-26 15:22 ` Philippe Mathieu-Daudé
2024-01-26 18:19 ` Manos Pitsidianakis
2024-01-29 8:24 ` Marc-André Lureau
2024-01-26 18:09 ` Alex Bennée
2024-01-26 18:15 ` Manos Pitsidianakis
2024-01-26 14:41 ` [PATCH v1 3/3] virtio-gpu-rutabaga.c: override resource_destroy method Manos Pitsidianakis
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=cover.1706279540.git.manos.pitsidianakis@linaro.org \
--to=manos.pitsidianakis@linaro.org \
--cc=gurchetansingh@chromium.org \
--cc=hi@alyssa.is \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--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).