From: Jani Nikula <jani.nikula@linux.intel.com>
To: Aaron Erhardt <aer@tuxedocomputers.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: Aaron Erhardt <aer@tuxedocomputers.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND RFC PATCH 1/1] drm: ensure that vblank diff is never negative
Date: Fri, 09 Jan 2026 10:18:08 +0200 [thread overview]
Message-ID: <686ae9c3d4697956d16eff0b6f2e6e43cb25ba90@intel.com> (raw)
In-Reply-To: <20260108165139.1381835-2-aer@tuxedocomputers.com>
On Thu, 08 Jan 2026, Aaron Erhardt <aer@tuxedocomputers.com> wrote:
> Handle cases, where drivers report incorrect timestamps and negative
> time differences are calculated. If the negative difference is large
> enough, negative missed vblanks are reported, but stored in an unsigned
> integer which can causes freezes. This patch prevents this case.
>
> This fix has been verified to fix problems with the i915 driver on
> modern Intel CPUs (e.g. Intel Core Ultra 7 155H).
Is there a reported bug about this, preferrably with logs? If not,
please file one as instructed at [1], and reference the patch.
BR,
Jani.
[1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
>
> Signed-off-by: Aaron Erhardt <aer@tuxedocomputers.com>
> ---
> drivers/gpu/drm/drm_vblank.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_vblank.c b/drivers/gpu/drm/drm_vblank.c
> index 94e45ed6869d..1022b6d61e4e 100644
> --- a/drivers/gpu/drm/drm_vblank.c
> +++ b/drivers/gpu/drm/drm_vblank.c
> @@ -1563,7 +1563,14 @@ static void drm_vblank_restore(struct drm_device *dev, unsigned int pipe)
> } while (cur_vblank != __get_vblank_counter(dev, pipe) && --count > 0);
>
> diff_ns = ktime_to_ns(ktime_sub(t_vblank, vblank->time));
> - if (framedur_ns)
> +
> + /*
> + * Make sure no bogus diffs result from negative differences
> + * when incorrect timestamps are reported by a driver.
> + */
> + if (drm_WARN_ON_ONCE(dev, t_vblank < vblank->time))
> + diff = 0;
> + else if (framedur_ns)
> diff = DIV_ROUND_CLOSEST_ULL(diff_ns, framedur_ns);
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-01-09 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:51 [RESEND RFC PATCH 0/1] " Aaron Erhardt
2026-01-08 16:51 ` [RESEND RFC PATCH 1/1] " Aaron Erhardt
2026-01-09 8:18 ` Jani Nikula [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=686ae9c3d4697956d16eff0b6f2e6e43cb25ba90@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=aer@tuxedocomputers.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=simona@ffwll.ch \
--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®