mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ruben Wauters <rubenru09@aol.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, Sophie D <patches@scd31.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org,  linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/gud: Ignore damage clips in full update mode
Date: Sat, 12 Sep 2026 13:21:38 +0100	[thread overview]
Message-ID: <bd5c58d759ab5808d0729f01d590e63a8841765e.camel@aol.com> (raw)
In-Reply-To: <987a45d3-2765-4583-b417-6aae5d350c45@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]

On Thu, 2026-09-10 at 08:17 +0200, Thomas Zimmermann wrote:
> 
> Am 10.09.26 um 03:49 schrieb Sophie D:
> > When running in full update mode, previously small updates (such as
> > moving the mouse across the screen) would cause many full frames to be
> > generated. This would bog down the bus and lower the effective framerate
> > significantly - I was seeing a drop from 60 FPS to 2 FPS.
> > 
> > Set ignore_damage_clips in full update mode so the damage iterator
> > yields a single full-plane rectangle instead of one per clip.
> > 
> > Fixes: 73cfd166e045 ("drm/gud: Replace simple display pipe with DRM atomic helpers")
> > Cc: <stable@vger.kernel.org> # 6.18.x
> > Signed-off-by: Sophie D <patches@scd31.com>
> 
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Acked-by: Ruben Wauters <rubenru09@aol.com>
> 
> Thanks for the fix.
> 
> > ---
> > v2: set ignore_damage_clips in atomic_check instead of merging clips in
> >      atomic_update (Thomas Zimmermann)
> > 
> >   drivers/gpu/drm/gud/gud_pipe.c | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/gud/gud_pipe.c b/drivers/gpu/drm/gud/gud_pipe.c
> > index 5ef887d84..3388fdc8e 100644
> > --- a/drivers/gpu/drm/gud/gud_pipe.c
> > +++ b/drivers/gpu/drm/gud/gud_pipe.c
> > @@ -482,6 +482,9 @@ int gud_plane_atomic_check(struct drm_plane *plane,
> >   	if (!new_plane_state->visible)
> >   		return 0;
> >   
> > +	if (gdrm->flags & GUD_DISPLAY_FLAG_FULL_UPDATE)
> > +		new_plane_state->ignore_damage_clips = true;
> > +
> >   	if (old_plane_state->rotation != new_plane_state->rotation)
> >   		crtc_state->mode_changed = true;
> >   

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 870 bytes --]

      reply	other threads:[~2026-09-12 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 23:08 [PATCH] drm/gud: Merge " Sophie D
2026-09-08  6:32 ` Thomas Zimmermann
2026-09-10  1:59   ` Sophie D
2026-09-10  1:49 ` [PATCH v2] drm/gud: Ignore " Sophie D
2026-09-10  6:17   ` Thomas Zimmermann
2026-09-12 12:21     ` Ruben Wauters [this message]

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=bd5c58d759ab5808d0729f01d590e63a8841765e.camel@aol.com \
    --to=rubenru09@aol.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=patches@scd31.com \
    --cc=simona@ffwll.ch \
    --cc=stable@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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

all inboxes | Powered by JetHome®