From: "Jahagirdar, Akshata" <akshata.jahagirdar@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 2/3] tests/intel/xe_ccs: require flat CCS on xe2
Date: Sun, 4 Feb 2024 21:45:28 -0800 [thread overview]
Message-ID: <e9499aa6-34f0-4333-a5ba-27935cc3e42c@intel.com> (raw)
In-Reply-To: <20240202073101.qdi3phnk23ma3j2r@zkempczy-mobl2>
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
On 2/1/2024 11:31 PM, Zbigniew Kempczyński wrote:
> On Thu, Feb 01, 2024 at 09:34:27PM -0800, Jahagirdar, Akshata wrote:
>
>> +
>> 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?
>
> Please fix your email client, it's hard to extract the answer.
>
> Regarding above - may you elaborate?
>
> --
> Zbigniew
Hi, sorry about that. not sure why it didn't quote properly before. Hope
it is fixed now.
So, regarding my previous comment, The BLT_CMD_SUPPORTS_COMPRESSION flag
checks if the "block-copy command" supports compression or not.
However, due to the unified compression in xe2+, we don't need to use
specific blitter commands to use compression any more.
So, i wanted to say that this flag checking compression support doesn't
make sense anymore for xe2, but I understand it would be different based
on platform specific .cmds_info.
I didn't check it properly before.
So anyway: Reviewed-by: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
-Akshata
>> - Akshata
>>
>> Do we have any Xe2 without compression on block-copy?
>>
>> --
>> Zbigniew
>>
>>
>>
>> --
>> 2.43.0
[-- Attachment #2: Type: text/html, Size: 3405 bytes --]
next prev parent reply other threads:[~2024-02-05 5:52 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
2024-02-02 7:31 ` Zbigniew Kempczyński
2024-02-05 5:45 ` Jahagirdar, Akshata [this message]
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=e9499aa6-34f0-4333-a5ba-27935cc3e42c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox