From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: Mohammed Thasleem <mohammed.thasleem@intel.com>,
igt-dev@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com
Subject: Re: [v4,2/2] tests/intel/kms_frontbuffer_tracking: Enable the tests support variations based on the WAs
Date: Mon, 9 Jun 2025 16:22:22 +0530 [thread overview]
Message-ID: <4fddf697-f3a1-4269-a9b5-4d4e3217879d@intel.com> (raw)
In-Reply-To: <20250601124355.16351-1-mohammed.thasleem@intel.com>
Hello Thasleem,
On 01-06-2025 18:13, Mohammed Thasleem wrote:
> This update stops skipping fbc-* tests support variations based on the WAs.
>
> v2: Use WA_FBC_DISABLED instead CHECK_WA. (Vinod)
> Update igt_skip_on_f discription. (Vinod)
> v3: Remove platform check and make it for xe specific. (Vinod)
> Rename function name with is_fbc_support. (Vinod)
> v4: Update function name and add igt_skip_on_f at calling function. (Vinod)
>
> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
> Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
> tests/intel/kms_frontbuffer_tracking.c | 23 +++++++++++++++++------
> 1 file changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/tests/intel/kms_frontbuffer_tracking.c b/tests/intel/kms_frontbuffer_tracking.c
> index 0809352cb..66a5177fe 100644
> --- a/tests/intel/kms_frontbuffer_tracking.c
> +++ b/tests/intel/kms_frontbuffer_tracking.c
> @@ -781,6 +781,7 @@
> */
>
> #define TIME SLOW_QUICK(1000, 10000)
> +#define WA_FBC_DISABLED "16023588340"
>
> IGT_TEST_DESCRIPTION("Test the Kernel's frontbuffer tracking mechanism and "
> "its related features: FBC, PSR and DRRS");
> @@ -2248,6 +2249,16 @@ static void do_flush(const struct test_mode *t)
>
> #define ASSERT_NO_IDLE_GPU (1 << 11)
>
> +static bool is_fbc_supported(int devid, const struct test_mode *t)
> +{
> + int wa;
> +
> + wa = igt_has_intel_wa(drm.fd, WA_FBC_DISABLED);
> + igt_assert_f(wa >= 0, "WA path not found on GTs\n");
> +
> + return wa != 1;
> +}
Better to move this to a new helper (kms_fbc_helper.c) or some library
since kms_dirtyfb, kms_fbcon_fbt, kms_psr and kms_psr2_sf may require
similar check.
Apart from that LGTM, you can have my rb on both patch of the series.
Reviewed-by: Kunal Joshi <kunal1.joshi@intel.com>
> +
> static int adjust_assertion_flags(const struct test_mode *t, int flags)
> {
> if (!(flags & DONT_ASSERT_FEATURE_STATUS)) {
> @@ -2610,8 +2621,8 @@ static void prepare_subtest_data(const struct test_mode *t,
> static void prepare_subtest_screens(const struct test_mode *t)
> {
> /* FBC disabled: Wa_16023588340 */
> - igt_skip_on_f((IS_BATTLEMAGE(drm.devid) && t->feature == FEATURE_FBC),
> - "FBC isn't supported on BMG\n");
> + igt_skip_on_f(t->feature == FEATURE_FBC && !is_fbc_supported(drm.devid, t),
> + "WA has disabled FBC on BMG\n");
>
> if (t->pipes == PIPE_DUAL)
> enable_both_screens_and_wait(t);
> @@ -2658,8 +2669,8 @@ static void prepare_subtest(const struct test_mode *t,
> static void rte_subtest(const struct test_mode *t)
> {
> /* FBC disabled: Wa_16023588340 */
> - igt_skip_on_f((IS_BATTLEMAGE(drm.devid) && t->feature == FEATURE_FBC),
> - "FBC isn't supported on BMG\n");
> + igt_skip_on_f(t->feature == FEATURE_FBC && !is_fbc_supported(drm.devid, t),
> + "WA has disabled FBC on BMG\n");
>
> prepare_subtest_data(t, NULL);
>
> @@ -4157,8 +4168,8 @@ igt_main_args("", long_options, help_str, opt_handler, NULL)
> t.tiling = opt.tiling;
>
> /* FBC disabled: Wa_16023588340 */
> - igt_skip_on_f((IS_BATTLEMAGE(drm.devid) && t.feature == FEATURE_FBC),
> - "FBC isn't supported on BMG\n");
> + igt_skip_on_f(t.feature == FEATURE_FBC && !is_fbc_supported(drm.devid, &t),
> + "WA has disabled FBC on BMG\n");
>
> for_each_pipe(&drm.display, pipe) {
> if (pipe == default_pipe) {
next prev parent reply other threads:[~2025-06-09 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 7:58 [PATCH v4 0/2] Refine FBC test conditions Mohammed Thasleem
2025-05-30 7:58 ` [PATCH v4 1/2] lib/igt_debugfs: Add specific checks for WA in GTs Mohammed Thasleem
2025-05-30 10:00 ` Govindapillai, Vinod
2025-05-30 7:58 ` [PATCH v3 2/2] tests/intel/kms_frontbuffer_tracking: Enable the tests support variations based on the WAs Mohammed Thasleem
2025-05-30 10:15 ` Govindapillai, Vinod
2025-06-01 12:43 ` [PATCH v4 " Mohammed Thasleem
2025-06-09 10:52 ` Joshi, Kunal1 [this message]
2025-05-30 8:40 ` ✓ Xe.CI.BAT: success for Refine FBC test conditions (rev3) Patchwork
2025-05-30 8:50 ` ✓ i915.CI.BAT: " Patchwork
2025-05-30 10:37 ` ✓ i915.CI.Full: " Patchwork
2025-05-31 10:06 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-01 13:16 ` ✓ Xe.CI.BAT: success for Refine FBC test conditions (rev4) Patchwork
2025-06-01 13:27 ` ✗ i915.CI.BAT: failure " Patchwork
2025-06-01 22:30 ` ✗ Xe.CI.Full: " 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=4fddf697-f3a1-4269-a9b5-4d4e3217879d@intel.com \
--to=kunal1.joshi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mohammed.thasleem@intel.com \
--cc=vinod.govindapillai@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