Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] i915/guc: Accumulate active runtime on gt reset
Date: Thu, 5 Dec 2024 14:11:02 -0800	[thread overview]
Message-ID: <e4b3529e-42ab-40cf-9b38-1a75f5ea7da2@intel.com> (raw)
In-Reply-To: <20241127174006.190128-4-umesh.nerlige.ramappa@intel.com>

On 11/27/2024 09:40, Umesh Nerlige Ramappa wrote:
> On gt reset, if a context is running, then accumulate it's active time
> into the busyness counter since there will be no chance for the context
> to switch out and update it's run time.
>
> v2: Move comment right above the if (John)
>
> Fixes: 77cdd054dd2c ("drm/i915/pmu: Connect engine busyness stats from GuC to pmu")
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>

> ---
>   drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 15 ++++++++++++++-
>   1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index 56be9f385270..2876024041a7 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -1449,8 +1449,21 @@ static void __reset_guc_busyness_stats(struct intel_guc *guc)
>   
>   	guc_update_pm_timestamp(guc, &unused);
>   	for_each_engine(engine, gt, id) {
> +		struct intel_engine_guc_stats *stats = &engine->stats.guc;
> +
>   		guc_update_engine_gt_clks(engine);
> -		engine->stats.guc.prev_total = 0;
> +
> +		/*
> +		 * If resetting a running context, accumulate the active
> +		 * time as well since there will be no context switch.
> +		 */
> +		if (stats->running) {
> +			u64 clk = guc->timestamp.gt_stamp - stats->start_gt_clk;
> +
> +			stats->total_gt_clks += clk;
> +		}
> +		stats->prev_total = 0;
> +		stats->running = 0;
>   	}
>   
>   	spin_unlock_irqrestore(&guc->timestamp.lock, flags);


  reply	other threads:[~2024-12-05 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 17:40 [PATCH 0/3] Fix some races/bugs in GuC engine busyness Umesh Nerlige Ramappa
2024-11-27 17:40 ` [PATCH 1/3] i915/guc: Reset engine utilization buffer before registration Umesh Nerlige Ramappa
2024-11-27 17:40 ` [PATCH 2/3] i915/guc: Ensure busyness counter increases motonically Umesh Nerlige Ramappa
2024-11-27 17:40 ` [PATCH 3/3] i915/guc: Accumulate active runtime on gt reset Umesh Nerlige Ramappa
2024-12-05 22:11   ` John Harrison [this message]
2024-11-27 18:42 ` ✗ Fi.CI.SPARSE: warning for Fix some races/bugs in GuC engine busyness (rev4) Patchwork
2024-11-27 18:57 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-27 20:36 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-13  6:28   ` Umesh Nerlige Ramappa
2024-12-14  0:16 ` [PATCH 0/3] Fix some races/bugs in GuC engine busyness Umesh Nerlige Ramappa
  -- strict thread matches above, loose matches on Subject: below --
2024-11-18 23:22 Umesh Nerlige Ramappa
2024-11-18 23:22 ` [PATCH 3/3] i915/guc: Accumulate active runtime on gt reset Umesh Nerlige Ramappa
2024-11-22  0:37   ` John Harrison
2024-11-25 20:12     ` Umesh Nerlige Ramappa

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=e4b3529e-42ab-40cf-9b38-1a75f5ea7da2@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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