All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Mika Kuoppala" <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix gpu frequency change tracing
Date: Wed, 18 Nov 2015 12:13:21 +0200	[thread overview]
Message-ID: <87oaerd39a.fsf@intel.com> (raw)
In-Reply-To: <20151117162532.GW4437@intel.com>

On Tue, 17 Nov 2015, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Nov 17, 2015 at 06:14:26PM +0200, Mika Kuoppala wrote:
>> With gen < 9 we have had always 50Mhz units as our hw
>> ratio. With gen >= 9 the hw ratio changed to 16.667Mhz (50/3).
>> The result was that our gpu frequency tracing started to output
>> values 3 times larger than expected due to hardcoded scaling
>> value. Fix this by using  Use intel_gpu_freq() when generating Mhz
>> value from ratio for 'intel_gpu_freq_change' trace event.
>> 
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92591
>> Reported-by: Eero Tamminen <eero.t.tamminen@intel.com>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>> ---
>>  drivers/gpu/drm/i915/intel_pm.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>> index ebd6735..656c53a 100644
>> --- a/drivers/gpu/drm/i915/intel_pm.c
>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>> @@ -4330,7 +4330,7 @@ static void gen6_set_rps(struct drm_device *dev, u8 val)
>>  	POSTING_READ(GEN6_RPNSWREQ);
>>  
>>  	dev_priv->rps.cur_freq = val;
>> -	trace_intel_gpu_freq_change(val * 50);
>> +	trace_intel_gpu_freq_change(intel_gpu_freq(dev_priv, val));
>
> I was thinking maybe moving it to the caller to avoid having it in both
> the gen6 and vlv set_rps functions, but there are actually so many callers
> that we're better off leaving it here.
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Pushed to drm-intel-fixes with cc: stable for v4.3+, thanks for the
patch and review.

BR,
Jani.


>
>>  }
>>  
>>  static void valleyview_set_rps(struct drm_device *dev, u8 val)
>> -- 
>> 2.5.0
>> 
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-11-18 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 16:14 [PATCH] drm/i915: Fix gpu frequency change tracing Mika Kuoppala
2015-11-17 16:25 ` Ville Syrjälä
2015-11-18 10:13   ` Jani Nikula [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=87oaerd39a.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.intel.com \
    --cc=ville.syrjala@linux.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.