From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Dump perf_limit_reasons for debug
Date: Mon, 26 Jun 2023 23:43:24 -0700 [thread overview]
Message-ID: <87jzvp5rsj.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <8c1b95aa-29c3-35dd-d0cc-609449a6730c@intel.com>
On Mon, 26 Jun 2023 21:02:14 -0700, Belgaumkar, Vinay wrote:
>
>
> On 6/26/2023 8:17 PM, Dixit, Ashutosh wrote:
> > On Mon, 26 Jun 2023 19:12:18 -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.
> >>
> >> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> 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..73911536a8e7 100644
> >> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> >> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> >> @@ -254,6 +254,8 @@ static int guc_wait_ucode(struct intel_guc *guc)
> >> 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, "perf limit reasons = 0x%08X\n",
> >> + intel_uncore_read(uncore, intel_gt_perf_limit_reasons_reg(gt)));
> > Maybe just add at the end of the previous guc_warn?
>
> Its already too long a line. If I try adding on the next line checkpatch
> complains about splitting double quotes.
In these cases of long quoted lines we generally ignore checkpatch. Because
perf limit reasons is part of the "excessive init time" message it should
be on the same line within the square brackets. So should not be
splitting double quotes.
Another idea would be something like this:
guc_warn(guc, "excessive init time: %lldms! [freq = %dMHz, before = %dMHz, status = 0x%08X]\n",
delta_ms, intel_rps_read_actual_frequency(&uncore->gt->rps),
before_freq, status);
guc_warn(guc, "excessive init time: [count = %d, ret = %d, perf limit reasons = 0x%08X]\n",
count, ret, intel_uncore_read(uncore, intel_gt_perf_limit_reasons_reg(gt)));
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2023-06-27 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 2:12 [Intel-gfx] [PATCH] drm/i915/guc: Dump perf_limit_reasons for debug Vinay Belgaumkar
2023-06-27 3:17 ` Dixit, Ashutosh
2023-06-27 4:02 ` Belgaumkar, Vinay
2023-06-27 6:43 ` Dixit, Ashutosh [this message]
2023-06-27 19:03 ` Belgaumkar, Vinay
2023-06-27 8:14 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " 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=87jzvp5rsj.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox