From: Matthew Brost <matthew.brost@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <lucas.demarchi@intel.com>
Subject: Re: [PATCH 1/2] drm/xe: Use a helper to get delta run ticks from the exec queue
Date: Tue, 25 Jun 2024 17:13:14 +0000 [thread overview]
Message-ID: <Znr6qpiO4d0OdpsG@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240625165812.58411-2-umesh.nerlige.ramappa@intel.com>
On Wed, Jun 26, 2024 at 12:58:11AM +0800, Umesh Nerlige Ramappa wrote:
> As per earlier review feedback - code manipulating exec queue fields
> should not be present in xe_device.c. Use a helper to get the delta run
> ticks from exec queue.
>
> Fixes: ce62827bc294 ("drm/xe: Do not access xe file when updating exec queue run_ticks")
I'm not sure if fixes applies here this is not changing behavior. Maybe
ask a maintainer for clarification here.
Patch itself is a good cleanup and looks correct.
With a clarification on the fixes tag usage:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> ---
> drivers/gpu/drm/xe/xe_drm_client.c | 7 ++-----
> drivers/gpu/drm/xe/xe_exec_queue.c | 18 ++++++++++++++++++
> drivers/gpu/drm/xe/xe_exec_queue.h | 1 +
> 3 files changed, 21 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_drm_client.c b/drivers/gpu/drm/xe/xe_drm_client.c
> index 4a19b771e3a0..e0c4a50d372c 100644
> --- a/drivers/gpu/drm/xe/xe_drm_client.c
> +++ b/drivers/gpu/drm/xe/xe_drm_client.c
> @@ -251,11 +251,8 @@ static void show_run_ticks(struct drm_printer *p, struct drm_file *file)
>
> /* Accumulate all the exec queues from this client */
> mutex_lock(&xef->exec_queue.lock);
> - xa_for_each(&xef->exec_queue.xa, i, q) {
> - xe_exec_queue_update_run_ticks(q);
> - xef->run_ticks[q->class] += q->run_ticks - q->old_run_ticks;
> - q->old_run_ticks = q->run_ticks;
> - }
> + xa_for_each(&xef->exec_queue.xa, i, q)
> + xef->run_ticks[q->class] += xe_exec_queue_delta_run_ticks(q);
> mutex_unlock(&xef->exec_queue.lock);
>
> /* Get the total GPU cycles */
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
> index 0ba37835849b..4d90a16745d2 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
> @@ -786,6 +786,24 @@ void xe_exec_queue_update_run_ticks(struct xe_exec_queue *q)
> q->run_ticks += (new_ts - old_ts) * q->width;
> }
>
> +/**
> + * xe_exec_queue_delta_run_ticks() - Get delta of queue run_ticks
> + * @q: The exec queue
> + *
> + * Update run ticks for the specific queue and then return the delta when
> + * compared to the previous value of run ticks.
> + */
> +u64 xe_exec_queue_delta_run_ticks(struct xe_exec_queue *q)
> +{
> + u64 delta_ticks;
> +
> + xe_exec_queue_update_run_ticks(q);
> + delta_ticks = q->run_ticks - q->old_run_ticks;
> + q->old_run_ticks = q->run_ticks;
> +
> + return delta_ticks;
> +}
> +
> void xe_exec_queue_kill(struct xe_exec_queue *q)
> {
> struct xe_exec_queue *eq = q, *next;
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.h b/drivers/gpu/drm/xe/xe_exec_queue.h
> index 289a3a51d2a2..42f683e5d88a 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue.h
> +++ b/drivers/gpu/drm/xe/xe_exec_queue.h
> @@ -76,5 +76,6 @@ struct dma_fence *xe_exec_queue_last_fence_get(struct xe_exec_queue *e,
> void xe_exec_queue_last_fence_set(struct xe_exec_queue *e, struct xe_vm *vm,
> struct dma_fence *fence);
> void xe_exec_queue_update_run_ticks(struct xe_exec_queue *q);
> +u64 xe_exec_queue_delta_run_ticks(struct xe_exec_queue *q);
>
> #endif
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-06-25 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 16:58 [PATCH 0/2] Capture per client stats when destroying an exec queue Umesh Nerlige Ramappa
2024-06-25 16:58 ` [PATCH 1/2] drm/xe: Use a helper to get delta run ticks from the " Umesh Nerlige Ramappa
2024-06-25 17:13 ` Matthew Brost [this message]
2024-06-25 16:58 ` [PATCH 2/2] drm/xe: Record utilization before destroying " Umesh Nerlige Ramappa
2024-06-25 17:24 ` Matthew Brost
2024-06-25 17:41 ` Matthew Brost
2024-06-26 3:21 ` Umesh Nerlige Ramappa
2024-06-27 6:01 ` Matthew Brost
2024-06-27 20:58 ` Lucas De Marchi
2024-06-29 0:47 ` Matthew Brost
2024-06-27 20:45 ` Lucas De Marchi
2024-06-25 17:03 ` ✓ CI.Patch_applied: success for Capture per client stats when destroying an " Patchwork
2024-06-25 17:03 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-25 17:04 ` ✓ CI.KUnit: success " Patchwork
2024-06-25 17:16 ` ✓ CI.Build: " Patchwork
2024-06-25 17:18 ` ✗ CI.Hooks: failure " Patchwork
2024-06-25 17:20 ` ✓ CI.checksparse: success " Patchwork
2024-06-25 17:49 ` ✗ CI.BAT: failure " Patchwork
2024-06-25 21:06 ` ✗ 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=Znr6qpiO4d0OdpsG@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=umesh.nerlige.ramappa@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