From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 4/7] lib/intel_bufops: Drop tilings restrictions
Date: Fri, 26 Apr 2024 13:14:21 +0300 [thread overview]
Message-ID: <7503f603-b901-457a-b963-aa00e2933ca5@gmail.com> (raw)
In-Reply-To: <20240425155259.yyuqzhlldbmtj7sx@zkempczy-mobl2>
On 25.4.2024 18.52, Zbigniew Kempczyński wrote:
> On Thu, Apr 25, 2024 at 04:08:23PM +0300, Juha-Pekka Heikkila wrote:
>> On 25.4.2024 13.47, Zbigniew Kempczyński wrote:
>>> Different platforms supports different tilings so instead of asserting
>>> on buffer creation path move responsibility of passing valid data
>>> to the test. It can use intel_cmds_info to iterate over supported
>>> tilings so this is better extendible and requires fewer changes.
>>>
>>> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
>>> ---
>>> lib/intel_bufops.c | 3 ---
>>> 1 file changed, 3 deletions(-)
>>>
>>> diff --git a/lib/intel_bufops.c b/lib/intel_bufops.c
>>> index 007ccdb953..b96275e485 100644
>>> --- a/lib/intel_bufops.c
>>> +++ b/lib/intel_bufops.c
>>> @@ -898,9 +898,6 @@ static void __intel_buf_init(struct buf_ops *bops,
>>> if (compression) {
>>> igt_require(bops->intel_gen >= 9);
>>> - igt_assert(req_tiling == I915_TILING_Y ||
>>> - req_tiling == I915_TILING_Yf ||
>>> - req_tiling == I915_TILING_4);
>>
>> I'm wondering if it would make sense to flip this assert around instead of
>> removing it? I mean would check here will not arrive linear and x-tile? I
>> didn't check but I assume this compression flag will not be enabled for xe2?
>
> I'm using this path to create compressed on xe2 and render-copy works
> fine on linear/x/4/64 there.
But do you hit this assert with xe2? I was thinking you wouldn't hit
that assert because compression is handled through pat index and from
that would follow with xe2 you'd never have compression flag set. Then
for dg2 you'd come here with also with tile64 so you could just check no
x-tile and linear are coming here.
Then again, looking at what's inside that if(){..} maybe you could just
change that "if (compression)" to something like "if
(!HAS_FLATCCS(intel_get_drm_devid(bops->fd))" and remove the inner if
doing the same thing?
/Juha-Pekka
next prev parent reply other threads:[~2024-04-26 10:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 10:47 [PATCH i-g-t 0/7] Add render-copy compression on Xe+ Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 1/7] lib/intel_bufops: Store devid on buffer ops creation Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 2/7] lib/intel_blt: Rename confusing fb tile to i915 tile Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 3/7] lib/intel_blt: Add i915 -> blt tile helper converter Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 4/7] lib/intel_bufops: Drop tilings restrictions Zbigniew Kempczyński
2024-04-25 13:08 ` Juha-Pekka Heikkila
2024-04-25 15:52 ` Zbigniew Kempczyński
2024-04-26 10:14 ` Juha-Pekka Heikkila [this message]
2024-04-26 11:22 ` Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 5/7] lib/intel_bufops: Start supporting compression on Xe2+ Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 6/7] lib/rendercopy_gen9: Allow to use all tilings on flatccs platforms Zbigniew Kempczyński
2024-04-25 12:26 ` Juha-Pekka Heikkila
2024-04-25 15:53 ` Zbigniew Kempczyński
2024-04-26 8:21 ` Zbigniew Kempczyński
2024-04-25 10:47 ` [PATCH i-g-t 7/7] tests/xe_render_copy: Add subtest which exercises compression Zbigniew Kempczyński
2024-04-25 11:43 ` ✓ CI.xeBAT: success for Add render-copy compression on Xe+ Patchwork
2024-04-25 11:49 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-26 3:59 ` Zbigniew Kempczyński
2024-04-26 7:59 ` Illipilli, TejasreeX
2024-04-25 23:59 ` ✗ CI.xeFULL: " Patchwork
2024-04-26 7:56 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-26 10:06 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-06 7:27 ` Zbigniew Kempczyński
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=7503f603-b901-457a-b963-aa00e2933ca5@gmail.com \
--to=juhapekka.heikkila@gmail.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