From: Karthik B S <karthik.b.s@intel.com>
To: Naladala Ramanaidu <ramanaidu.naladala@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: <uma.shankar@intel.com>, <mitulkumar.ajitkumar.golani@intel.com>,
<arun.r.murthy@intel.com>
Subject: Re: [PATCH i-g-t v1 2/2] tests/kms_flip: Remove assertion dependency on link reset retry condition
Date: Tue, 1 Jul 2025 20:23:53 +0530 [thread overview]
Message-ID: <3974b663-c745-49a8-bc1f-9ed12e76ffc1@intel.com> (raw)
In-Reply-To: <20250701110149.395301-3-ramanaidu.naladala@intel.com>
Hi Ramanaidu,
On 7/1/2025 4:31 PM, Naladala Ramanaidu wrote:
> This change avoids test failures in scenarios where hotplug detection
> is inconclusive or delayed. The call to link reset is retained for
> its potential side effects or logging purposes, but it is no longer
> part of the assertion condition.
>
> Signed-off-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com>
> ---
> tests/kms_flip.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 4dfa1c483..8ce164202 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -1641,7 +1641,9 @@ retry:
>
> /* quiescent the hw a bit so ensure we don't miss a single frame */
> if (o->flags & TEST_CHECK_TS && !calibrate_ts(o, crtc_idxs[0])) {
> - igt_assert(!retried && needs_retry_after_link_reset(mon));
> + igt_assert(!retried);
> +
> + needs_retry_after_link_reset(mon);
Moving this out of the assert will need changes in the function
definition as currently it is returning a 'bool'. Also does having it
standalone(outside assert) add any additional value?
Regards,
Karthik.B.S
>
> retried = true;
>
> @@ -1680,7 +1682,9 @@ retry:
> state_ok &= check_final_state(o, &o->vblank_state, elapsed);
>
> if (!state_ok) {
> - igt_assert(!retried && needs_retry_after_link_reset(mon));
> + igt_assert(!retried);
> +
> + needs_retry_after_link_reset(mon);
>
> retried = true;
>
next prev parent reply other threads:[~2025-07-01 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 11:01 [PATCH i-g-t v1 0/2] Relax link reset and frame rate checks Naladala Ramanaidu
2025-07-01 11:01 ` [PATCH i-g-t v1 1/2] tests/kms_flip: Adjust pass rate threshold based on frame rate Naladala Ramanaidu
2025-07-01 14:46 ` Karthik B S
2025-07-01 11:01 ` [PATCH i-g-t v1 2/2] tests/kms_flip: Remove assertion dependency on link reset retry condition Naladala Ramanaidu
2025-07-01 14:53 ` Karthik B S [this message]
2025-07-01 12:33 ` ✓ Xe.CI.BAT: success for Relax link reset and frame rate checks Patchwork
2025-07-01 12:42 ` ✓ i915.CI.BAT: " Patchwork
2025-07-02 5:42 ` ✗ i915.CI.Full: failure " Patchwork
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=3974b663-c745-49a8-bc1f-9ed12e76ffc1@intel.com \
--to=karthik.b.s@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=ramanaidu.naladala@intel.com \
--cc=uma.shankar@intel.com \
/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