Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion
Date: Mon, 30 Sep 2024 13:34:36 -0700	[thread overview]
Message-ID: <ZvsLXNoZN5LgA17g@orsosgc001> (raw)
In-Reply-To: <20240918195330.3167756-2-ashutosh.dixit@intel.com>

On Wed, Sep 18, 2024 at 12:53:23PM -0700, Ashutosh Dixit wrote:
>When we introduce xe_syncs, we don't wait for internal OA programming
>batches to complete. That is, xe_syncs are signaled asynchronously. In
>anticipation for this, separate out batch submission from waiting for
>completion of those batches.
>
>v2: Change return type of xe_oa_submit_bb to "struct dma_fence *" (Matt B)
>v3: Retain init "int err = 0;" in xe_oa_submit_bb (Jose)
>
>Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
>Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>---
> drivers/gpu/drm/xe/xe_oa.c | 57 +++++++++++++++++++++++++++++---------
> 1 file changed, 44 insertions(+), 13 deletions(-)
>
>diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
>index 354ee9045efc8..52805e159e6fd 100644
>--- a/drivers/gpu/drm/xe/xe_oa.c
>+++ b/drivers/gpu/drm/xe/xe_oa.c
>@@ -570,11 +570,10 @@ static __poll_t xe_oa_poll(struct file *file, poll_table *wait)
> 	return ret;
> }
>
>-static int xe_oa_submit_bb(struct xe_oa_stream *stream, struct xe_bb *bb)
>+static struct dma_fence *xe_oa_submit_bb(struct xe_oa_stream *stream, struct xe_bb *bb)
> {
> 	struct xe_sched_job *job;
> 	struct dma_fence *fence;
>-	long timeout;
> 	int err = 0;
>
> 	/* Kernel configuration is issued on stream->k_exec_q, not stream->exec_q */
>@@ -588,14 +587,9 @@ static int xe_oa_submit_bb(struct xe_oa_stream *stream, struct xe_bb *bb)
> 	fence = dma_fence_get(&job->drm.s_fence->finished);
> 	xe_sched_job_push(job);
>
>-	timeout = dma_fence_wait_timeout(fence, false, HZ);
>-	dma_fence_put(fence);
>-	if (timeout < 0)
>-		err = timeout;
>-	else if (!timeout)
>-		err = -ETIME;
>+	return fence;
> exit:
>-	return err;
>+	return ERR_PTR(err);
> }
>
> static void write_cs_mi_lri(struct xe_bb *bb, const struct xe_oa_reg *reg_data, u32 n_regs)
>@@ -659,6 +653,7 @@ static void xe_oa_store_flex(struct xe_oa_stream *stream, struct xe_lrc *lrc,
> static int xe_oa_modify_ctx_image(struct xe_oa_stream *stream, struct xe_lrc *lrc,
> 				  const struct flex *flex, u32 count)
> {
>+	struct dma_fence *fence;
> 	struct xe_bb *bb;
> 	int err;
>
>@@ -670,7 +665,16 @@ static int xe_oa_modify_ctx_image(struct xe_oa_stream *stream, struct xe_lrc *lr
>
> 	xe_oa_store_flex(stream, lrc, bb, flex, count);
>
>-	err = xe_oa_submit_bb(stream, bb);
>+	fence = xe_oa_submit_bb(stream, bb);
>+	if (IS_ERR(fence)) {
>+		err = PTR_ERR(fence);
>+		goto free_bb;
>+	}
>+	xe_bb_free(bb, fence);
>+	dma_fence_put(fence);
>+
>+	return 0;
>+free_bb:
> 	xe_bb_free(bb, NULL);
> exit:
> 	return err;

Just a nit - if you initialize fence and err, then this will be as 
below.  Note that if fence is NULL, dma_fence_put doesn't do anything.

{
	struct dma_fence *fence = NULL;
	struct xe_bb *bb;
	int err = 0;
...
	fence = xe_oa_submit_bb(stream, bb);
	if (IS_ERR(fence))
		err = PTR_ERR(fence);

	xe_bb_free(bb, NULL);
	dma_fence_put(fence);
exit:
	return err;
}

otherwise, lgtm

Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

	

>@@ -678,6 +682,7 @@ static int xe_oa_modify_ctx_image(struct xe_oa_stream *stream, struct xe_lrc *lr
>
> static int xe_oa_load_with_lri(struct xe_oa_stream *stream, struct xe_oa_reg *reg_lri)
> {
>+	struct dma_fence *fence;
> 	struct xe_bb *bb;
> 	int err;
>
>@@ -689,7 +694,16 @@ static int xe_oa_load_with_lri(struct xe_oa_stream *stream, struct xe_oa_reg *re
>
> 	write_cs_mi_lri(bb, reg_lri, 1);
>
>-	err = xe_oa_submit_bb(stream, bb);
>+	fence = xe_oa_submit_bb(stream, bb);
>+	if (IS_ERR(fence)) {
>+		err = PTR_ERR(fence);
>+		goto free_bb;
>+	}
>+	xe_bb_free(bb, fence);
>+	dma_fence_put(fence);
>+
>+	return 0;
>+free_bb:
> 	xe_bb_free(bb, NULL);
> exit:
> 	return err;
>@@ -922,15 +936,32 @@ static int xe_oa_emit_oa_config(struct xe_oa_stream *stream, struct xe_oa_config
> {
> #define NOA_PROGRAM_ADDITIONAL_DELAY_US 500
> 	struct xe_oa_config_bo *oa_bo;
>-	int err, us = NOA_PROGRAM_ADDITIONAL_DELAY_US;
>+	int err = 0, us = NOA_PROGRAM_ADDITIONAL_DELAY_US;
>+	struct dma_fence *fence;
>+	long timeout;
>
>+	/* Emit OA configuration batch */
> 	oa_bo = xe_oa_alloc_config_buffer(stream, config);
> 	if (IS_ERR(oa_bo)) {
> 		err = PTR_ERR(oa_bo);
> 		goto exit;
> 	}
>
>-	err = xe_oa_submit_bb(stream, oa_bo->bb);
>+	fence = xe_oa_submit_bb(stream, oa_bo->bb);
>+	if (IS_ERR(fence)) {
>+		err = PTR_ERR(fence);
>+		goto exit;
>+	}
>+
>+	/* Wait till all previous batches have executed */
>+	timeout = dma_fence_wait_timeout(fence, false, 5 * HZ);
>+	dma_fence_put(fence);
>+	if (timeout < 0)
>+		err = timeout;
>+	else if (!timeout)
>+		err = -ETIME;
>+	if (err)
>+		drm_dbg(&stream->oa->xe->drm, "dma_fence_wait_timeout err %d\n", err);
>
> 	/* Additional empirical delay needed for NOA programming after registers are written */
> 	usleep_range(us, 2 * us);
>-- 
>2.41.0
>

  reply	other threads:[~2024-09-30 20:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 19:53 [PATCH v6 0/7] drm/xe/oa: xe_syncs for OA Ashutosh Dixit
2024-09-18 19:53 ` [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion Ashutosh Dixit
2024-09-30 20:34   ` Umesh Nerlige Ramappa [this message]
2024-09-18 19:53 ` [PATCH 2/7] drm/xe/oa/uapi: Define and parse OA sync properties Ashutosh Dixit
2024-09-18 19:53 ` [PATCH 3/7] drm/xe/oa: Add input fence dependencies Ashutosh Dixit
2024-09-18 19:53 ` [PATCH 4/7] drm/xe/oa: Signal output fences Ashutosh Dixit
2024-09-18 19:53 ` [PATCH 5/7] drm/xe/oa: Move functions up so they can be reused for config ioctl Ashutosh Dixit
2024-09-18 19:53 ` [PATCH 6/7] drm/xe/oa: Add syncs support to OA " Ashutosh Dixit
2024-09-18 19:53 ` [PATCH 7/7] drm/xe/oa: Allow only certain property changes from config Ashutosh Dixit
2024-09-18 23:10 ` ✓ CI.Patch_applied: success for drm/xe/oa: xe_syncs for OA (rev6) Patchwork
2024-09-18 23:10 ` ✓ CI.checkpatch: " Patchwork
2024-09-18 23:11 ` ✓ CI.KUnit: " Patchwork
2024-09-18 23:23 ` ✓ CI.Build: " Patchwork
2024-09-18 23:25 ` ✓ CI.Hooks: " Patchwork
2024-09-18 23:27 ` ✓ CI.checksparse: " Patchwork
2024-09-18 23:45 ` ✓ CI.BAT: " Patchwork
2024-09-19 14:07 ` ✗ CI.FULL: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-10-22 20:03 [PATCH v7 0/7] drm/xe/oa: xe_syncs for OA Ashutosh Dixit
2024-10-22 20:03 ` [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion Ashutosh Dixit
2024-08-30 22:16 [PATCH v5 0/7] drm/xe/oa: xe_syncs for OA Ashutosh Dixit
2024-08-30 22:16 ` [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion Ashutosh Dixit
2024-08-28  1:50 [PATCH v4 0/7] drm/xe/oa: xe_syncs for OA Ashutosh Dixit
2024-08-28  1:50 ` [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion Ashutosh Dixit
2024-08-21 15:28 [PATCH v3 0/7] drm/xe/oa: xe_syncs for OA Ashutosh Dixit
2024-08-21 15:28 ` [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion Ashutosh Dixit
2024-08-20  0:58 [PATCH v2 0/7] drm/xe/oa: xe_syncs for OA Ashutosh Dixit
2024-08-20  0:58 ` [PATCH 1/7] drm/xe/oa: Separate batch submission from waiting for completion Ashutosh Dixit

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=ZvsLXNoZN5LgA17g@orsosgc001 \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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