From: sashiko-bot@kernel.org
To: "Prike Liang" <Prike.Liang@amd.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/5] drm/amd/display: send the flip event right away if vblank is off
Date: Wed, 11 Nov 2026 08:45:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-208631@kernel.org> (raw)
In-Reply-To: <20261111083534.514290-3-Prike.Liang@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] drm/amd/display: missing Signed-off-by trailer in commit
message
--
commit 26c603fc4a2cad18ac38e5e382079d6b467933c0
Author: Prike Liang <Prike.Liang@amd.com>
> drm/amd/display: send the flip event right away if vblank is off
>
> dm_arm_vblank_event_pre_programming() takes a vblank reference for a
> page flip or cursor update that carries an event, and the handler that
> later sends the event drops that reference again. The return value of
> drm_crtc_vblank_get() is ignored, though. If vblank is off, the event
> is armed anyway, and the handler that eventually sends it drops a
> reference that was never taken, which unbalances the vblank refcount.
>
> That can't happen today: DM only turns vblank off for a CRTC that it
> disables, and a disabled CRTC has no active planes. The next patch also
> turns vblank off while a GPU reset has the streams stopped, though.
> Page flips that don't modify the DC state skip
> amdgpu_dm_commit_streams() and only take dc_lock after this point, so
> they still get here while the reset holds it.
>
> Send the event right away when no vblank reference can be taken, like
> drm_crtc_vblank_off() does for queued vblank events. No vblank interrupt
> could deliver it in that case anyway.
>
> Add a KUnit test for it.
>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Leo Li <sunpeng.li@amd.com>
> Assisted-by: Copilot:claude-opus-5.5
[Severity: High]
This commit message is missing a Signed-off-by trailer from the patch
author.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111083534.514290-1-Prike.Liang@amd.com?part=3
next prev parent reply other threads:[~2026-11-11 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 8:35 [PATCH 1/5] drm/client: Make the FBIO_WAITFORVSYNC vblank wait interruptible Prike Liang
2026-11-11 8:35 ` [PATCH 2/5] drm/vblank: Stop drm_crtc_wait_one_vblank() when vblank is turned off Prike Liang
2026-11-11 8:45 ` sashiko-bot
2026-11-11 8:35 ` [PATCH 3/5] drm/amd/display: send the flip event right away if vblank is off Prike Liang
2026-11-11 8:45 ` sashiko-bot [this message]
2026-11-11 8:35 ` [PATCH 4/5] drm/amd/display: turn vblank off in DRM across GPU reset Prike Liang
2026-11-11 9:19 ` sashiko-bot
2026-11-11 8:35 ` [PATCH 5/5] drm/amdgpu: keep reading the vblank counter in IRQ context during reset Prike Liang
2026-11-11 9:09 ` sashiko-bot
2026-11-11 8:42 ` [PATCH 1/5] drm/client: Make the FBIO_WAITFORVSYNC vblank wait interruptible sashiko-bot
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=sashiko-outbox-208631@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Prike.Liang@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox