From: Matthew Auld <matthew.auld@intel.com>
To: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
Cc: igt-dev@lists.freedesktop.org, zbigniew.kempczynski@intel.com
Subject: Re: [PATCH i-g-t v1 3/3] tests/xe_ccs: Check if platform supports compression
Date: Tue, 26 Mar 2024 08:36:47 +0000 [thread overview]
Message-ID: <100fba34-b4d3-4b0f-9413-4f14345a8272@intel.com> (raw)
In-Reply-To: <1d66863d0c0ba1e70c8a668ed88a1ed69321e29f.1711444735.git.akshata.jahagirdar@intel.com>
On 26/03/2024 09:54, Akshata Jahagirdar wrote:
> Add check before running the test to ensure the platform supports
> compression and has flat ccs enabled.
>
> Signed-off-by: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
> ---
> tests/intel/xe_ccs.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/intel/xe_ccs.c b/tests/intel/xe_ccs.c
> index 8fe1f62eb..b424a1d6d 100644
> --- a/tests/intel/xe_ccs.c
> +++ b/tests/intel/xe_ccs.c
> @@ -718,6 +718,7 @@ igt_main_args("bf:pst:W:H:", NULL, help_str, opt_handler, NULL)
> igt_fixture {
> xe = drm_open_driver(DRIVER_XE);
> igt_require(blt_has_block_copy(xe));
> + igt_require(blt_platform_supports_compression(xe));
At least on Xe2 I think we still need some kind validation here, since
this is a valid user config. IIRC HW claims that we shouldn't really
care that flat-ccs is for example disabled by BIOS on LNL. Everything
should "just work", given that the CCS state is always zero. IMO test
should be updated to account for xe2 && compression_disabled to verify
that CCS state is indeed always zero on such a config.
> if (AT_LEAST_GEN(xe, 20))
> igt_require(HAS_FLATCCS(xe));
>
prev parent reply other threads:[~2024-03-26 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 9:54 [PATCH i-g-t v1 0/3] Add check to ensure platform supports compression Akshata Jahagirdar
2024-03-25 23:57 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2024-03-26 9:54 ` [PATCH i-g-t v1 1/3] drm-uapi/xe_drm: Read flat ccs value from drm_xe_query_config Akshata Jahagirdar
2024-03-26 5:19 ` Zbigniew Kempczyński
2024-03-26 5:29 ` Jahagirdar, Akshata
2024-03-26 6:03 ` Zbigniew Kempczyński
2024-03-26 9:54 ` [PATCH i-g-t v1 2/3] lib/intel_blt: Add helper function to ensure platform supports compression Akshata Jahagirdar
2024-03-26 9:54 ` [PATCH i-g-t v1 3/3] tests/xe_ccs: Check if " Akshata Jahagirdar
2024-03-26 8:36 ` Matthew Auld [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=100fba34-b4d3-4b0f-9413-4f14345a8272@intel.com \
--to=matthew.auld@intel.com \
--cc=akshata.jahagirdar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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