From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jeevan B <jeevan.b@intel.com>
Cc: igt-dev@lists.freedesktop.org, swati2.sharma@intel.com,
pranay.samala@intel.com
Subject: Re: [PATCH i-g-t] kms_flip_tiling: reduce exec time for sim env
Date: Wed, 8 Oct 2025 22:57:21 +0300 [thread overview]
Message-ID: <aObCIXt0HPVWwl3n@intel.com> (raw)
In-Reply-To: <20251008152540.1556189-1-jeevan.b@intel.com>
On Wed, Oct 08, 2025 at 08:55:40PM +0530, Jeevan B wrote:
> For simulation environment, we can reduce execution time
> by running test only with basic tiling combinations.
>
> v2: Add helper to check basic tiling support.
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/intel/kms_flip_tiling.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/tests/intel/kms_flip_tiling.c b/tests/intel/kms_flip_tiling.c
> index ff9ad1229..024421b58 100644
> --- a/tests/intel/kms_flip_tiling.c
> +++ b/tests/intel/kms_flip_tiling.c
> @@ -84,6 +84,13 @@ static int try_commit(igt_display_t *display)
> COMMIT_ATOMIC : COMMIT_LEGACY);
> }
>
> +static bool is_allowed_modifier(uint64_t mod)
That function name and implementation is extremely confusing.
Why are these allowed and nothing else? Nothing here tells me
any of that.
> +{
> + return mod == DRM_FORMAT_MOD_LINEAR ||
> + mod == I915_FORMAT_MOD_4_TILED ||
> + mod == I915_FORMAT_MOD_X_TILED;
> +}
> +
> static uint64_t pageflip_timeout_us(drmModeModeInfo *mode)
> {
> uint64_t timeout_ns;
> @@ -216,6 +223,7 @@ igt_main
> igt_describe("Check pageflip between modifiers");
> igt_subtest_with_dynamic("flip-change-tiling") {
> enum pipe pipe;
> + bool run_in_simulation = igt_run_in_simulation();
>
> for_each_pipe_with_valid_output(&data.display, pipe, output) {
> igt_plane_t *plane;
> @@ -242,6 +250,11 @@ igt_main
> if (plane->formats[j] != data.testformat)
> continue;
>
> + if (run_in_simulation &&
> + (!is_allowed_modifier(plane->modifiers[i]) ||
> + !is_allowed_modifier(plane->modifiers[j])))
> + continue;
> +
> igt_dynamic_f("pipe-%s-%s-%s-to-%s",
> kmstest_pipe_name(pipe),
> igt_output_name(output),
> --
> 2.43.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-10-08 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 15:25 [PATCH i-g-t] kms_flip_tiling: reduce exec time for sim env Jeevan B
2025-10-08 19:43 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-10-08 19:57 ` Ville Syrjälä [this message]
2025-10-09 3:17 ` [PATCH i-g-t] " B, Jeevan
2025-10-08 20:03 ` ✓ i915.CI.BAT: success for " Patchwork
2025-10-08 22:16 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-09 9:48 ` ✓ i915.CI.Full: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-10-09 6:29 [PATCH i-g-t] " Jeevan B
2025-10-09 16:25 ` Kamil Konieczny
2025-10-14 19:29 ` Sharma, Swati2
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=aObCIXt0HPVWwl3n@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=pranay.samala@intel.com \
--cc=swati2.sharma@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