From: Matthew Auld <matthew.auld@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/2] lib/intel_blt: use BYTE_COPY mode on xe2
Date: Wed, 24 Jan 2024 08:37:54 +0000 [thread overview]
Message-ID: <9ff41e6a-de8b-48c6-b341-e665423b9cf2@intel.com> (raw)
In-Reply-To: <20240124045608.5cph37f2evqkdsl2@zkempczy-mobl2>
On 24/01/2024 04:56, Zbigniew Kempczyński wrote:
> On Tue, Jan 23, 2024 at 06:33:23PM +0000, Matthew Auld wrote:
>> Currently we see various CAT errors and timeouts on xe2 when running
>> xe_copy_basic. If selecting PAGE_COPY mode for MEM_COPY, the page size
>> is defined as 256B block as xe2. Also the width should be defined in
>> number of pages, and not bytes, which likely explains the CAT errors.
>> However the caller in xe_copy_basic is not using a size that is aligned
>> to 256B, so rather just select the more general BYTE_COPY mode instead,
>> which should work for any reasonable number of bytes.
>>
>> BSpec: 57561
>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
>> ---
>> lib/intel_blt.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/intel_blt.c b/lib/intel_blt.c
>> index e41e261ea..25d251c4f 100644
>> --- a/lib/intel_blt.c
>> +++ b/lib/intel_blt.c
>> @@ -1613,7 +1613,7 @@ static void emit_blt_mem_copy(int fd, uint64_t ahnd, const struct blt_mem_data *
>> optype = mem->src.type == M_MATRIX ? 1 << 17 : 0;
>>
>> i = 0;
>> - batch[i++] = MEM_COPY_CMD | (1 << 19) | optype;
>> + batch[i++] = MEM_COPY_CMD | optype;
>> batch[i++] = mem->src.width - 1;
>> batch[i++] = mem->src.height - 1;
>> batch[i++] = mem->src.pitch - 1;
>> --
>> 2.43.0
>>
>
> +Sai
>
> At first glance I don't like removing (1 << 19). For M_MATRIX
> we require BYTE_COPY. I'm not sure Sai is working on such tests
> but we discussed offline sometime I would like to have such
> tests here.
This patch is enabling BYTE_COPY mode. Setting bit 19 turns on the
PAGE_COPY mode. Matrix Copy looks to require BYTE_COPY. Also there
doesn't seem to be a bit 19 on PVC, it seems to only support byte copy.
>
> --
> Zbigniew
next prev parent reply other threads:[~2024-01-24 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 18:33 [PATCH i-g-t 1/2] tests/intel/xe_copy_basic: account for prefetch Matthew Auld
2024-01-23 18:33 ` [PATCH i-g-t 2/2] lib/intel_blt: use BYTE_COPY mode on xe2 Matthew Auld
2024-01-24 4:56 ` Zbigniew Kempczyński
2024-01-24 8:37 ` Matthew Auld [this message]
2024-01-25 6:04 ` Zbigniew Kempczyński
2024-01-23 19:30 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] tests/intel/xe_copy_basic: account for prefetch Patchwork
2024-01-23 19:55 ` ✓ CI.xeBAT: " Patchwork
2024-01-24 4:45 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-24 4:48 ` [PATCH i-g-t 1/2] " Zbigniew Kempczyński
2024-01-24 8:42 ` Matthew Auld
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=9ff41e6a-de8b-48c6-b341-e665423b9cf2@intel.com \
--to=matthew.auld@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