From: Matthew Auld <matthew.auld@intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: add prefetch padding to store_dw batchbuffer
Date: Wed, 19 Oct 2022 10:14:18 +0100 [thread overview]
Message-ID: <ca42bc29-ef8c-cb36-a8f7-897c7baee0ca@intel.com> (raw)
In-Reply-To: <7c31859f-5afc-fc24-98c9-8a14bacd66cd@intel.com>
On 19/10/2022 10:12, Matthew Auld wrote:
> On 19/10/2022 08:12, Andrzej Hajda wrote:
>> Instruction prefetch mechanism requires that 512 bytes after the last
>> command should be readable by EU. Otherwise DMAR errors and engine
>> hangs can happen.
>>
>> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5278
>> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
>
> Is there a Bspec ref for this? I would have assumed that EU was more
> about kernels/shaders, than simple MI commands? Also should we be
> hitting dmar errors for ppGTT if this were some kind of overfetch?
> AFAICT we always point entries back to scratch, unlike with say the GGTT
> where we might have stale entries, and unbinding should flush the tlb?
s/unbinding/put_pages/
>
>> ---
>> drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c
>> b/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c
>> index 3c55e77b0f1b00..fe999a02f8e10a 100644
>> --- a/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c
>> +++ b/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c
>> @@ -50,7 +50,7 @@ igt_emit_store_dw(struct i915_vma *vma,
>> u32 *cmd;
>> int err;
>> - size = (4 * count + 1) * sizeof(u32);
>> + size = (4 * count + 1) * sizeof(u32) + 512;
>> size = round_up(size, PAGE_SIZE);
>> obj = i915_gem_object_create_internal(vma->vm->i915, size);
>> if (IS_ERR(obj))
next prev parent reply other threads:[~2022-10-19 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 7:12 [Intel-gfx] [PATCH] drm/i915/selftests: add prefetch padding to store_dw batchbuffer Andrzej Hajda
2022-10-19 8:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-10-19 9:12 ` [Intel-gfx] [PATCH] " Matthew Auld
2022-10-19 9:14 ` Matthew Auld [this message]
2022-10-19 11:01 ` Andrzej Hajda
2022-10-19 14:54 ` [Intel-gfx] ✗ Fi.CI.IGT: failure 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=ca42bc29-ef8c-cb36-a8f7-897c7baee0ca@intel.com \
--to=matthew.auld@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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