From: Lyude Paul <lyude@redhat.com>
To: dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
linux-kernel@lists.freedesktop.org
Cc: "Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"David Airlie" <airlied@redhat.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
linux-kernel@vger.kernel.org, "Simona Vetter" <simona@ffwll.ch>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maxime Ripard" <mripard@kernel.org>,
"Christian Hergert" <christian@sourceandstack.com>,
"Lyude Paul" <lyude@redhat.com>
Subject: [PATCH 0/2] drm/virtio: Damage clip fixes
Date: Thu, 3 Sep 2026 17:15:50 -0400 [thread overview]
Message-ID: <20260903211914.1109100-1-lyude@redhat.com> (raw)
A previous associate of mine asked if someone would be able to help with
upstreaming some work that they had done recently for virtio, and I was
more then happy to help. These fixes help maintain FB damage clips
between framebuffer changes, which were previously discarded even when
userspace provided accumulated per-buffer damage.
Patches apply on top of drm-misc/drm-misc-next.
Christian Hergert (2):
drm/virtio: preserve damage clips for rendered resources
drm/virtio: Recalculate ignore_damage_clips on every update
drivers/gpu/drm/virtio/virtgpu_plane.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
base-commit: f9c2f70ee41544717b3c209083073db1e21f919b
--
2.55.0
next reply other threads:[~2026-09-03 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 21:15 Lyude Paul [this message]
2026-09-03 21:15 ` [PATCH 1/2] drm/virtio: preserve damage clips for rendered resources Lyude Paul
2026-09-03 21:15 ` [PATCH 2/2] drm/virtio: Recalculate ignore_damage_clips on every update Lyude Paul
2026-09-03 21:27 ` sashiko-bot
2026-09-07 12:45 ` [PATCH 0/2] drm/virtio: Damage clip fixes 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=20260903211914.1109100-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@redhat.com \
--cc=christian@sourceandstack.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.