From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/guc: Dump perf_limit_reasons for debug
Date: Tue, 27 Jun 2023 14:20:01 -0700 [thread overview]
Message-ID: <87ilb861ry.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230627191336.319381-1-vinay.belgaumkar@intel.com>
On Tue, 27 Jun 2023 12:13:36 -0700, Vinay Belgaumkar wrote:
>
> GuC load takes longer sometimes due to GT frequency not ramping up.
> Add perf_limit_reasons to the existing warn print to see if frequency
> is being throttled.
>
> v2: Review comments (Ashutosh)
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> index 364d0d546ec8..0f79cb658518 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> @@ -251,9 +251,11 @@ static int guc_wait_ucode(struct intel_guc *guc)
> if (ret == 0)
> ret = -ENXIO;
> } else if (delta_ms > 200) {
> - guc_warn(guc, "excessive init time: %lldms! [freq = %dMHz, before = %dMHz, status = 0x%08X, count = %d, ret = %d]\n",
> - delta_ms, intel_rps_read_actual_frequency(&uncore->gt->rps),
> - before_freq, status, count, ret);
> + guc_warn(guc, "excessive init time: %lldms! [status = 0x%08X, count = %d, ret = %d]\n",
> + delta_ms, status, count, ret);
> + guc_warn(guc, "excessive init time: [freq = %dMHz, before = %dMHz, perf_limit_reasons = 0x%08X]\n",
> + intel_rps_read_actual_frequency(&uncore->gt->rps), before_freq,
> + intel_uncore_read(uncore, intel_gt_perf_limit_reasons_reg(gt)));
> } else {
> guc_dbg(guc, "init took %lldms, freq = %dMHz, before = %dMHz, status = 0x%08X, count = %d, ret = %d\n",
> delta_ms, intel_rps_read_actual_frequency(&uncore->gt->rps),
> --
> 2.38.1
>
next prev parent reply other threads:[~2023-06-27 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 19:13 [Intel-gfx] [PATCH v2] drm/i915/guc: Dump perf_limit_reasons for debug Vinay Belgaumkar
2023-06-27 19:13 ` Vinay Belgaumkar
2023-06-27 21:20 ` Dixit, Ashutosh [this message]
2023-06-27 23:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Dump perf_limit_reasons for debug (rev2) Patchwork
2023-06-28 17:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-29 18:12 ` Belgaumkar, Vinay
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=87ilb861ry.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.