All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simona Vetter <simona.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/atomic: Filter out redundant DPMS calls
Date: Fri, 28 Feb 2025 21:47:05 +0200	[thread overview]
Message-ID: <Z8ISuRz2l9Om9tC_@intel.com> (raw)
In-Reply-To: <Z7b7tSabXeLe1ovT@phenom.ffwll.local>

On Thu, Feb 20, 2025 at 10:53:57AM +0100, Simona Vetter wrote:
> On Wed, Feb 19, 2025 at 06:02:39PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Video players (eg. mpv) do periodic XResetScreenSaver() calls to
> > keep the screen on while the video playing. The modesetting ddx
> > plumbs these straight through into the kernel as DPMS setproperty
> > ioctls, without any filtering whatsoever. When implemented via
> > atomic these end up as full commits on the crtc, which leads to a
> > dropped frame every time XResetScreenSaver() is called.
> 
> I think you should add here that it's just an empty commit, because we do
> filter out redundant commits where crtc->active_changed does nothing.
> Except we still run the entire machinery with timestamps and drm_event and
> everything.
> 
> And I don't think it's worth to filter that out at the atomic level,
> because it's really only legacy ioctl that had this "complete noop"
> behaviour.
> 
> With the commit message augmented:
> 
> Reviewed-by: Simona Vetter <simona.vetter@ffwll.ch>
> 
> Might also be nice to have a igt for this?

kms_flip was basically doing everything we want already,
so added one more subtest for this:
https://lore.kernel.org/igt-dev/20250228194240.20023-1-ville.syrjala@linux.intel.com/T/#u

> Plus also wondering whether we
> should cc: stable it.

I guess we could. I've been running this for who knows how long
anyway (just never got around to sending it), so should be fairly
safe.

-- 
Ville Syrjälä
Intel

      parent reply	other threads:[~2025-02-28 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 16:02 [PATCH] drm/atomic: Filter out redundant DPMS calls Ville Syrjala
2025-02-19 17:06 ` Hamza Mahfooz
2025-02-19 19:10   ` Ville Syrjälä
2025-02-19 17:55 ` ✓ i915.CI.BAT: success for " Patchwork
2025-02-20  7:11 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-20  9:53 ` [PATCH] " Simona Vetter
2025-02-20 10:00   ` Simona Vetter
2025-02-20 15:27     ` Ville Syrjälä
2025-02-21 14:42       ` Simona Vetter
2025-02-28 19:47   ` Ville Syrjälä [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=Z8ISuRz2l9Om9tC_@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=simona.vetter@ffwll.ch \
    /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.