Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karolina Stolarek <karolina.stolarek@intel.com>
To: <juhapekka.heikkila@gmail.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] lib/igt_fb: include lib/intel_blt functions to blitter path
Date: Fri, 30 Jun 2023 09:20:13 +0200	[thread overview]
Message-ID: <d085ea43-0f4d-24f7-11dd-0278d68587d7@intel.com> (raw)
In-Reply-To: <ed84e5dd-e80e-b65a-1f12-3123029b41c5@gmail.com>


On 29.06.2023 18:04, Juha-Pekka Heikkila wrote:
<big snip>

>>>>> +            blt_set_copy_object(&blt.src, src);
>>>>> +            blt_set_copy_object(&blt.dst, dst);
>>>>> +
>>>>> +            if (HAS_FLATCCS(intel_get_drm_devid(src_fb->fd))) {
>>>>
>>>> This check might not be correct on some platforms. To check if we 
>>>> need to fill in ext part, you could do a similar check as in commit 
>>>> 45da871dd268 ("tests/gem_ccs: Check for extended block-copy and 
>>>> compression support").
>>>>
>>>> +Zbigniew, what is the status of HAS_FLATCCS? How is it useful in 
>>>> the context of blitter copy? I believe we want to switch to using 
>>>> command flags, like BLT_CMD_EXTENDED? Or am I misremembering something?
>>>>
>>>
>>> This is bit double edged situation. Even if for MTL there would be 
>>> added support for compression into intel_blt, all the related 
>>> handling for aux ccs would still not be here on igt_fb.c. For flat 
>>> ccs everything that is needed is now in place and for time being it 
>>> seems correct, everything matches. Do note this in not only 
>>> controlled by HAS_FLATCCS() but also by modifiers which actually 
>>> arrive onto this part of code.
>>
>> Hmm, I see, let's leave it for now and we can revisit it in the future.
>>
>> Thanks for answering my questions. Like I said, there are two nits 
>> that would be good to tidy up, but everything else looks good to me:
>>
>> Reviewed-by: Karolina Stolarek <karolina.stolarek@intel.com>
> 
> Thanks Karolina. In the mean time this patch was separated into two 
> parts, one where there were couple of more Xe related changes and other 
> where these blitting related changes. May I use this R-b here
> 
> https://patchwork.freedesktop.org/patch/544642/?series=119886&rev=4

Yes, please do

> ?
> 
> Those few alignment fixes and small adjustments I'll apply before 
> pushing if I will not need another ci round.

I think you're good to go, the reported regressions seem unrelated to 
your patches.

Many thanks,
Karolina

> 
> /Juha-Pekka

  reply	other threads:[~2023-06-30  7:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 17:22 [igt-dev] [PATCH i-g-t 0/3] Include intel_blt funtions to blitter path for igt_fb.c Juha-Pekka Heikkila
2023-06-27 17:22 ` [igt-dev] [PATCH i-g-t 1/3] lib/intel_blt: Add offset to block and fast copy Juha-Pekka Heikkila
2023-06-27 17:22 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_fb: include lib/intel_blt functions to blitter path Juha-Pekka Heikkila
2023-06-28  7:52   ` Modem, Bhanuprakash
2023-06-28 17:39     ` Juha-Pekka Heikkila
2023-06-29  8:45   ` Karolina Stolarek
2023-06-29 11:17     ` Juha-Pekka Heikkila
2023-06-29 11:51       ` Karolina Stolarek
2023-06-29 16:04         ` Juha-Pekka Heikkila
2023-06-30  7:20           ` Karolina Stolarek [this message]
2023-06-27 17:22 ` [igt-dev] [PATCH i-g-t 3/3] lib/igt_fb: On blitter path take clear color modifier into account Juha-Pekka Heikkila
2023-06-28  7:53   ` Modem, Bhanuprakash
2023-06-27 18:08 ` [igt-dev] ✗ GitLab.Pipeline: warning for Include intel_blt funtions to blitter path for igt_fb.c (rev2) Patchwork
2023-06-27 18:42 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-28 10:01 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-06-26 19:57 [igt-dev] [PATCH i-g-t 0/3] Include intel_blt funtions to blitter path for igt_fb.c Juha-Pekka Heikkila
2023-06-26 19:57 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_fb: include lib/intel_blt functions to blitter path Juha-Pekka Heikkila

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=d085ea43-0f4d-24f7-11dd-0278d68587d7@intel.com \
    --to=karolina.stolarek@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.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