From: "Jahagirdar, Akshata" <akshata.jahagirdar@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Matthew Auld" <matthew.auld@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 2/3] tests/intel/xe_ccs: require flat CCS on xe2
Date: Thu, 1 Feb 2024 21:34:27 -0800 [thread overview]
Message-ID: <b749b213-424d-4211-be41-e8fa25a00bf2@intel.com> (raw)
In-Reply-To: <20240201211441.b5yncl7w2pn6dwk4@zkempczy-mobl2>
[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]
On 2/1/2024 1:14 PM, Zbigniew Kempczyński wrote:
> On Thu, Feb 01, 2024 at 10:30:16AM +0000, Matthew Auld wrote:
>> On Xe2 compression is handled via PAT indexes and flat CCS, even on
>> igpu. Ensure the device has flat CCS support on such hardware, to
>> determine if these tests are valid.
>>
>> v2: (Zbigniew)
>> - There is at least one uncompressed test also, which is valid
>> regardless of CCS. Move the skip deeper.
>>
>> Signed-off-by: Matthew Auld<matthew.auld@intel.com>
>> Cc: Akshata Jahagirdar<akshata.jahagirdar@intel.com>
>> Cc: Zbigniew Kempczyński<zbigniew.kempczynski@intel.com>
>> ---
>> tests/intel/xe_ccs.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/tests/intel/xe_ccs.c b/tests/intel/xe_ccs.c
>> index 7d0e8ed7a..3430db2d2 100644
>> --- a/tests/intel/xe_ccs.c
>> +++ b/tests/intel/xe_ccs.c
>> @@ -532,6 +532,7 @@ static void block_copy_test(int xe,
>> struct igt_collection *set,
>> enum copy_func copy_function)
>> {
>> + uint16_t dev_id = intel_get_drm_devid(xe);
>> struct drm_xe_engine_class_instance inst = {
>> .engine_class = DRM_XE_ENGINE_CLASS_COPY,
>> };
>> @@ -540,6 +541,9 @@ static void block_copy_test(int xe,
>> uint32_t vm, exec_queue;
>> int tiling;
>>
>> + if (AT_LEAST_GEN(dev_id, 20) && config->compression)
>> + igt_require(HAS_FLATCCS(xe));
> Just to make sure - above will lead to skip on xe2 if there's
> no flatccs.
>
>> +
>> if (config->compression && !blt_block_copy_supports_compression(xe))
>> return;
> This will check compression either, but indirectly via .cmds_info
> set to xe2_cmds_info in which we use BLT_CMD_SUPPORTS_COMPRESSION
> flag for block-copy command.
on a side note, IIUC the BLT_CMD_SUPPORTS_COMPRESSION flag doesn't make
sense anymore due to xe2+ unified compression?
- Akshata
> Do we have any Xe2 without compression on block-copy?
>
> --
> Zbigniew
>
>>
>> --
>> 2.43.0
>>
[-- Attachment #2: Type: text/html, Size: 3186 bytes --]
next prev parent reply other threads:[~2024-02-02 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 10:30 [PATCH i-g-t v2 1/3] lib/intel_device_info: set has_flatccs on LNL Matthew Auld
2024-02-01 10:30 ` [PATCH i-g-t v2 2/3] tests/intel/xe_ccs: require flat CCS on xe2 Matthew Auld
2024-02-01 21:14 ` Zbigniew Kempczyński
2024-02-02 5:34 ` Jahagirdar, Akshata [this message]
2024-02-02 7:31 ` Zbigniew Kempczyński
2024-02-05 5:45 ` Jahagirdar, Akshata
2024-02-02 9:48 ` Zbigniew Kempczyński
2024-02-01 10:30 ` [PATCH i-g-t v2 3/3] tests/intel/xe_pat: assert flat CSS support for xe2 Matthew Auld
2024-02-02 5:49 ` Jahagirdar, Akshata
2024-02-01 13:06 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/3] lib/intel_device_info: set has_flatccs on LNL Patchwork
2024-02-01 13:46 ` ✓ CI.xeBAT: " Patchwork
2024-02-01 15:20 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-02 5:33 ` [PATCH i-g-t v2 1/3] " Jahagirdar, Akshata
2024-02-02 11:24 ` Kamil Konieczny
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=b749b213-424d-4211-be41-e8fa25a00bf2@intel.com \
--to=akshata.jahagirdar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.