From: Karolina Stolarek <karolina.stolarek@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_ccs: Use extended block-copy on MTL
Date: Fri, 20 Jan 2023 08:35:08 +0100 [thread overview]
Message-ID: <fdce235d-9927-1bcd-a4aa-ba1009c4ff57@intel.com> (raw)
In-Reply-To: <20230119142929.127976-1-zbigniew.kempczynski@intel.com>
On 19.01.2023 15:29, Zbigniew Kempczyński wrote:
> Integrated platforms and DG1 (exception in discrete, doesn't have
> flatccs) use shorter version of block-copy blit (12 dwords length,
> extended command use 22 dwords). MTL is first integrated which uses
> extended block-copy instruction.
>
> At the moment change enables using block-copy for uncompressed blits
> on MTL only due to fact aux-ccs support for blitter is still unclear
> for me. We haven't before code which uses aux-ccs for blitter so
> enablement of this might occur in future changes.
>
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
> tests/i915/gem_ccs.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_ccs.c b/tests/i915/gem_ccs.c
> index ff28c6d889..6ae5ad85b8 100644
> --- a/tests/i915/gem_ccs.c
> +++ b/tests/i915/gem_ccs.c
> @@ -443,6 +443,7 @@ static void block_copy(int i915,
> uint32_t run_id = mid_tiling;
> uint32_t mid_region = region2, bb;
> uint32_t width = param.width, height = param.height;
> + uint32_t devid = intel_get_drm_devid(i915);
> enum blt_compression mid_compression = config->compression;
> int mid_compression_format = param.compression_format;
> enum blt_compression_type comp_type = COMPRESSION_TYPE_3D;
> @@ -451,7 +452,7 @@ static void block_copy(int i915,
>
> igt_assert(__gem_create_in_memory_regions(i915, &bb, &bb_size, region1) == 0);
>
> - if (!blt_supports_compression(i915))
> + if (!blt_supports_compression(i915) && !IS_METEORLAKE(devid))
This is fine as a temporary change -- I think we'll be able to handle
this case with blt_tiling_info patches, but for now:
Reviewed-by: Karolina Stolarek <karolina.stolarek@intel.com>
Thanks,
Karolina
> pext = NULL;
>
> src = create_object(i915, region1, width, height, bpp, uc_mocs,
next prev parent reply other threads:[~2023-01-20 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 14:29 [igt-dev] [PATCH i-g-t] i915/gem_ccs: Use extended block-copy on MTL Zbigniew Kempczyński
2023-01-19 15:36 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-20 7:35 ` Karolina Stolarek [this message]
2023-01-20 7:42 ` [igt-dev] [PATCH i-g-t] " Zbigniew Kempczyński
2023-01-20 13:48 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
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=fdce235d-9927-1bcd-a4aa-ba1009c4ff57@intel.com \
--to=karolina.stolarek@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