From: "Maíra Canal" <mcanal@igalia.com>
To: Maxime Ripard <mripard@kernel.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] drm/vc4: tests: Retry pv-muxing tests when EDEADLK
Date: Sun, 23 Mar 2025 15:07:59 -0300 [thread overview]
Message-ID: <e3517bd6-a9c2-4193-92d8-b6510b967d0a@igalia.com> (raw)
In-Reply-To: <20250318-drm-vc4-kunit-failures-v1-4-779864d9ab37@kernel.org>
Hi Maxime,
On 18/03/25 11:17, Maxime Ripard wrote:
> Some functions used by the HVS->PV muxing tests can return with EDEADLK,
> meaning the entire sequence should be restarted. It's not a fatal error
> and we should treat it as a recoverable error, and recover, instead of
> failing the test like we currently do.
>
> Fixes: 76ec18dc5afa ("drm/vc4: tests: Add unit test suite for the PV muxing")
> Signed-off-by: Maxime Ripard <mripard@kernel.org>
> ---
> drivers/gpu/drm/vc4/tests/vc4_test_pv_muxing.c | 44 ++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/drivers/gpu/drm/vc4/tests/vc4_test_pv_muxing.c b/drivers/gpu/drm/vc4/tests/vc4_test_pv_muxing.c
> index 52c04ef33206bf4f9e21e3c8b7cea932824a67fa..94e05bddb630a79aab189d9bc16f09a9d84ce396 100644
> --- a/drivers/gpu/drm/vc4/tests/vc4_test_pv_muxing.c
> +++ b/drivers/gpu/drm/vc4/tests/vc4_test_pv_muxing.c
> @@ -685,20 +685,26 @@ static void drm_vc4_test_pv_muxing(struct kunit *test)
>
> drm_modeset_acquire_init(&ctx, 0);
>
> vc4 = priv->vc4;
> drm = &vc4->base;
> +
> +retry:
> state = drm_kunit_helper_atomic_state_alloc(test, drm, &ctx);
> KUNIT_ASSERT_NOT_ERR_OR_NULL(test, state);
> for (i = 0; i < params->nencoders; i++) {
> enum vc4_encoder_type enc_type = params->encoders[i];
>
> ret = vc4_mock_atomic_add_output(test, state, enc_type);
> + if (ret == -EDEADLK)
> + goto retry;
> KUNIT_ASSERT_EQ(test, ret, 0);
> }
>
> ret = drm_atomic_check_only(state);
> + if (ret == -EDEADLK)
> + goto retry;
Shouldn't we call `drm_modeset_backoff()` before retrying (maybe
`drm_atomic_state_clear()` as well)?
Best Regards,
- Maíra
> KUNIT_EXPECT_EQ(test, ret, 0);
>
> KUNIT_EXPECT_TRUE(test,
> check_fifo_conflict(test, state));
>
prev parent reply other threads:[~2025-03-23 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 14:17 [PATCH 0/4] drm/vc4: tests: Fix locking failures Maxime Ripard
2025-03-18 14:17 ` [PATCH 1/4] drm/vc4: tests: Use return instead of assert Maxime Ripard
2025-03-23 18:12 ` Maíra Canal
2025-03-18 14:17 ` [PATCH 2/4] drm/vc4: tests: Document output handling functions Maxime Ripard
2025-03-23 18:34 ` Maíra Canal
2025-03-28 15:30 ` Maxime Ripard
2025-03-18 14:17 ` [PATCH 3/4] drm/vc4: tests: Stop allocating the state in test init Maxime Ripard
2025-03-23 18:48 ` Maíra Canal
2025-03-28 15:32 ` Maxime Ripard
2025-03-30 18:10 ` Maíra Canal
2025-03-18 14:17 ` [PATCH 4/4] drm/vc4: tests: Retry pv-muxing tests when EDEADLK Maxime Ripard
2025-03-23 18:07 ` Maíra Canal [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=e3517bd6-a9c2-4193-92d8-b6510b967d0a@igalia.com \
--to=mcanal@igalia.com \
--cc=airlied@gmail.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-list@raspberrypi.com \
--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®