All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com,
	andi.shyti@linux.intel.com, anshuman.gupta@intel.com
Subject: Re: [PATCH v1] drm/i915/selftest: Change throttle criteria for rps
Date: Sun, 12 Jan 2025 09:34:17 +0200	[thread overview]
Message-ID: <Z4NweSvVpJcn2_Zk@black.fi.intel.com> (raw)
In-Reply-To: <sog7fejryo3zpyp2ekqk7wffgc7tueoxvkyntun6i7bqae5a3w@ljnv62saynkn>

On Sat, Jan 11, 2025 at 09:41:47PM +0100, Andi Shyti wrote:
> Hi Raag,
> 
> On Thu, Jan 02, 2025 at 04:36:18PM +0530, Raag Jadav wrote:
> > Current live_rps_control() implementation errors out on throttling.
> > This was done with the assumption that throttling to minimum frequency
> > is a catastrophic failure, which is incorrect. Throttling can happen
> > due to variety of reasons and often times out of our control. Also,
> > the resulting frequency can be at any given point below the maximum
> > allowed. Change throttle criteria to reflect this logic and drop the
> > error, as it doesn't necessarily mean selftest failure.
> > 
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> 
> Reviewed and merged to drm-intel-gt-next.

Thank you.

Sorry I didn't pick your tag as I considered this a different patch.

Raag

      reply	other threads:[~2025-01-12  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 11:06 [PATCH v1] drm/i915/selftest: Change throttle criteria for rps Raag Jadav
2025-01-02 11:38 ` ✓ i915.CI.BAT: success for " Patchwork
2025-01-02 13:22 ` ✓ i915.CI.Full: " Patchwork
2025-01-08  9:28 ` [PATCH v1] " Raag Jadav
2025-01-09 19:04   ` Rodrigo Vivi
2025-01-09 18:59 ` Belgaumkar, Vinay
2025-01-11 20:41 ` Andi Shyti
2025-01-12  7:34   ` Raag Jadav [this message]

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=Z4NweSvVpJcn2_Zk@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=andi.shyti@linux.intel.com \
    --cc=anshuman.gupta@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.