From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] drm/xe/tests: Wait for clear fence operation to complete
Date: Thu, 5 Dec 2024 15:35:01 +0100 [thread overview]
Message-ID: <46df595d-4b94-4f5d-8fde-2854fb70295f@linux.intel.com> (raw)
In-Reply-To: <01abf9d9-f1c4-4ac4-a69a-c9f1ae36bd4e@intel.com>
On 12/5/2024 12:49 PM, Matthew Auld wrote:
> On 05/12/2024 11:47, Nirmoy Das wrote:
>> Ensure the clear operation completes before proceeding, as the clear
>> fence is not attached to the BO's dma-resv object.
>>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>
> In theory it is all single timeline underneath, so the later copy job would anyway happen after the clear, and we should wait for that. So hopefully in practice this is not issue.
I haven't seen any issue caused by this yet but found it while looking into the IOMMU+CAT error issue.
>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Thanks,
Nirmoy
>
>> ---
>> drivers/gpu/drm/xe/tests/xe_bo.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/tests/xe_bo.c b/drivers/gpu/drm/xe/tests/xe_bo.c
>> index 3e0ae40ebbd2..c9ec7a313c6b 100644
>> --- a/drivers/gpu/drm/xe/tests/xe_bo.c
>> +++ b/drivers/gpu/drm/xe/tests/xe_bo.c
>> @@ -49,6 +49,13 @@ static int ccs_test_migrate(struct xe_tile *tile, struct xe_bo *bo,
>> KUNIT_FAIL(test, "Failed to submit bo clear.\n");
>> return PTR_ERR(fence);
>> }
>> +
>> + if (dma_fence_wait_timeout(fence, false, 5 * HZ) <= 0) {
>> + dma_fence_put(fence);
>> + KUNIT_FAIL(test, "Timeout while clearing bo.\n");
>> + return -ETIME;
>> + }
>> +
>> dma_fence_put(fence);
>> }
>>
>
next prev parent reply other threads:[~2024-12-05 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 11:47 [PATCH] drm/xe/tests: Wait for clear fence operation to complete Nirmoy Das
2024-12-05 11:49 ` Matthew Auld
2024-12-05 14:35 ` Nirmoy Das [this message]
2024-12-05 14:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-05 14:05 ` ✓ CI.checkpatch: " Patchwork
2024-12-05 14:06 ` ✓ CI.KUnit: " Patchwork
2024-12-05 14:25 ` ✓ CI.Build: " Patchwork
2024-12-05 14:27 ` ✓ CI.Hooks: " Patchwork
2024-12-05 14:28 ` ✓ CI.checksparse: " Patchwork
2024-12-05 14:58 ` ✗ Xe.CI.BAT: failure " Patchwork
2024-12-09 8:37 ` Nirmoy Das
2024-12-05 15:56 ` ✗ Xe.CI.Full: " 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=46df595d-4b94-4f5d-8fde-2854fb70295f@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=nirmoy.das@intel.com \
--cc=thomas.hellstrom@linux.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