From: Raag Jadav <raag.jadav@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, anshuman.gupta@intel.com,
chris.p.wilson@linux.intel.com
Subject: Re: [PATCH v1] drm/i915/selftest: Log throttle reasons on failure
Date: Tue, 10 Dec 2024 10:53:10 +0200 [thread overview]
Message-ID: <Z1gBdqXSCpJVjRmh@black.fi.intel.com> (raw)
In-Reply-To: <Z1cat34KiCX8U-gP@intel.com>
On Mon, Dec 09, 2024 at 11:28:39AM -0500, Rodrigo Vivi wrote:
> On Sat, Dec 07, 2024 at 08:14:42AM +0200, Raag Jadav wrote:
> > Cc: Chris
> >
> > On Fri, Dec 06, 2024 at 10:45:18AM -0500, Rodrigo Vivi wrote:
> > > On Thu, Dec 05, 2024 at 01:44:13PM +0530, Raag Jadav wrote:
> > > > Log throttle reasons on selftest failure which will be useful for
> > > > debugging.
> > > >
> > > > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/gt/selftest_rps.c | 7 +++++--
> > > > 1 file changed, 5 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/gt/selftest_rps.c b/drivers/gpu/drm/i915/gt/selftest_rps.c
> > > > index dcef8d498919..1e0e59bc69b6 100644
> > > > --- a/drivers/gpu/drm/i915/gt/selftest_rps.c
> > > > +++ b/drivers/gpu/drm/i915/gt/selftest_rps.c
> > > > @@ -478,8 +478,11 @@ int live_rps_control(void *arg)
> > > > min, max, ktime_to_ns(min_dt), ktime_to_ns(max_dt));
> > > >
> > > > if (limit == rps->min_freq) {
> > >
> > > I was going to merge this, but then I noticed that this prints only
> > > when the throttle moves that to our min_freq... When PCODE throttle
> > > the freq, the guaranteed freq can be at any point, not necessarily
> > > to the minimal, so this print is not very effective in the end of the day
> >
> > Makes me wonder why such a criteria at all?
>
> very good question...
> Perhaps we need to revamp entirely this selftest or kill it?
Depends. Do we qualify throttling as a failure?
If yes, we'll keep hitting this every now and then.
If no, then just dropping this condition might be enough.
Raag
> > > > - pr_err("%s: GPU throttled to minimum!\n",
> > > > - engine->name);
> > > > + u32 throttle = intel_uncore_read(gt->uncore,
> > > > + intel_gt_perf_limit_reasons_reg(gt));
> > > > +
> > > > + pr_err("%s: GPU throttled to minimum frequency with reasons 0x%08x\n",
> > > > + engine->name, throttle & GT0_PERF_LIMIT_REASONS_MASK);
> > > > show_pstate_limits(rps);
> > > > err = -ENODEV;
> > > > break;
> > > > --
> > > > 2.34.1
> > > >
next prev parent reply other threads:[~2024-12-10 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:14 [PATCH v1] drm/i915/selftest: Log throttle reasons on failure Raag Jadav
2024-12-05 13:20 ` Andi Shyti
2024-12-05 17:13 ` ✓ i915.CI.BAT: success for " Patchwork
2024-12-05 18:46 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-06 15:45 ` [PATCH v1] " Rodrigo Vivi
2024-12-07 6:14 ` Raag Jadav
2024-12-09 16:28 ` Rodrigo Vivi
2024-12-10 8:53 ` Raag Jadav [this message]
2024-12-10 22:38 ` Rodrigo Vivi
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=Z1gBdqXSCpJVjRmh@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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.