Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] intel-ci/xe: Update kms blocklist documentation
Date: Sun, 6 Aug 2023 23:28:02 +0530	[thread overview]
Message-ID: <4b6c7a4c-146f-c134-0f72-efa9fac4891a@intel.com> (raw)
In-Reply-To: <20230803122305.3887694-1-bhanuprakash.modem@intel.com>

Hi Bhanu,

Please find my comments inline.

On 03-Aug-23 5:53 PM, Bhanuprakash Modem wrote:
> Add justification to kms blocklist.
> 
> Cc: Swati Sharma <swati2.sharma@intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
>   tests/intel-ci/xe.blocklist.txt | 41 ++++++++++++++++++---------------
>   1 file changed, 22 insertions(+), 19 deletions(-)
> 
> diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
> index b40dd4f70..df7bb4149 100644
> --- a/tests/intel-ci/xe.blocklist.txt
> +++ b/tests/intel-ci/xe.blocklist.txt
> @@ -44,41 +44,44 @@ igt@syncobj_.*
>   igt@template
>   igt@tools_test
>   ##################################################################
> -# Pipe E, F, G and H
> +# KMS: Pipe E, F, G and H are not available on Intel hardware
>   ##################################################################
>   igt@.*@.*pipe-(e|f|g|h).*
> -##################################################################
> -# Multidisplay
> -##################################################################
>   igt@kms_bw@.*-(5|6|7|8)-displays-.*
>   ##################################################################
> +# KMS: Tests those are specific to i915 driver

 >>Nitpick: Tests specific to i915 driver

Also, can we precisely mention which all features are not supported
in xe in contrast to i915 and why we had to blacklist all these testcases.

> +##################################################################
> +igt@kms_busy@.*
>   igt@kms_draw_crc@draw-method-(mmap-cpu|mmap-gtt|pwrite)
> -igt@kms_draw_crc@fill-fb
> -igt@kms_pipe_b_c_ivb@.*
> -igt@kms_pwrite_crc
> -igt@kms_ccs@.*
> -igt@kms_frontbuffer_tracking@.*
> -igt@kms_fbcon_fbt@(fbc|psr)(-suspend)
>   igt@kms_fence_pin_leak
> -igt@kms_busy@.*
> -igt@kms_psr@.*_mmap_(cpu|gtt)
> -igt@kms_legacy_colorkey@basic
> -igt@kms_legacy_colorkey@invalid-plane
> -igt@kms_flip_scaled_crc@flip-(32|64)bpp-(4|x|y|yf|tileccs)tile-.*
> -igt@kms_big_fb@(4|x|y|yf)-tiled-.*
>   igt@kms_flip@2x-flip-vs-fences
>   igt@kms_flip@flip-vs-fences(-interruptible)
> +igt@kms_legacy_colorkey@basic
> +igt@kms_legacy_colorkey@invalid-plane

 >> These 2 can be combined together.

> +igt@kms_pipe_b_c_ivb@.*
> +igt@kms_psr@.*_mmap_(cpu|gtt)
> +igt@kms_pwrite_crc
> +igt@kms_rotation_crc@exhaust-fences
> +##################################################################
> +# KMS: IGT HANG & Tiling support is not ready.
> +# To be removed once IGT started supporting these features.
> +##################################################################

 >> Make as 2 categories (i) Hang (ii) Tiling

>   igt@kms_addfb_basic@clobberred-modifier
>   igt@kms_addfb_basic@.*-tiling
>   igt@kms_addfb_basic@.*-(4|x|y|yf)-.*
>   igt@kms_async_flips@.*
> -igt@kms_plane_multiple@tiling-(4|x|y|yf)
> +igt@kms_big_fb@(4|x|y|yf)-tiled-.*
> +igt@kms_ccs@.*
>   igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-(atomic|legacy)
> -igt@kms_rotation_crc@primary-(4|x|y|yf)-tiled-.*
> -igt@kms_rotation_crc@exhaust-fences
> +igt@kms_draw_crc@fill-fb
> +igt@kms_fbcon_fbt@(fbc|psr)(-suspend)

 >> Specific suspend tests are dependent on tiling?

> +igt@kms_flip_scaled_crc@flip-(32|64)bpp-(4|x|y|yf|tileccs)tile-.*
>   igt@kms_force_connector_basic@force-load-detect
> +igt@kms_frontbuffer_tracking@.*
>   igt@kms_getfb@.*-ccs
>   igt@kms_plane_lowres@tiling-(4|x|y|yf)
> +igt@kms_plane_multiple@tiling-(4|x|y|yf)
> +igt@kms_rotation_crc@primary-(4|x|y|yf)-tiled-.*
>   igt@kms_.*@.*hang.*
>   ##################################################################
>   igt@xe_sysfs*

      parent reply	other threads:[~2023-08-06 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 12:23 [igt-dev] [i-g-t] intel-ci/xe: Update kms blocklist documentation Bhanuprakash Modem
2023-08-03 13:37 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-08-03 13:45 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-03 18:36 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-06 17:58 ` Sharma, Swati2 [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=4b6c7a4c-146f-c134-0f72-efa9fac4891a@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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