Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/pmu: Report frequency as zero while GPU is sleeping
Date: Fri, 6 Dec 2019 13:04:20 +0000	[thread overview]
Message-ID: <9804a5e4-efad-1746-91f9-a327ccb55dfd@linux.intel.com> (raw)
In-Reply-To: <157563554404.8823.10550311749695088810@skylake-alporthouse-com>


On 06/12/2019 12:32, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-11-29 10:54:36)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> We used to report the minimum possible frequency as both requested and
>> active while GPU was in sleep state. This was a consequence of sampling
>> the value from the "current frequency" field in our software tracking.
>>
>> This was strictly speaking wrong, but given that until recently the
>> current frequency in sleeping state used to be equal to minimum, it did
>> not stand out sufficiently to be noticed as such.
>>
>> After some recent changes have made the current frequency be reported
>> as last active before GPU went to sleep, meaning both requested and active
>> frequencies could end up being reported at their maximum values for the
>> duration of the GPU idle state, it became much more obvious that this does
>> not make sense.
>>
>> To fix this we will now sample the frequency counters only when the GPU is
>> awake. As a consequence reported frequencies could be reported as below
>> the GPU reported minimum but that should be much less confusing that the
>> current situation.
>>
>> v2:
>>   * Split out early exit conditions for readability. (Chris)
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> I'm happy if you are happy...

Okay pushed, thanks!

Regards,

Tvrtko

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-06 13:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 16:10 [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping Tvrtko Ursulin
2019-11-28 16:10 ` [Intel-gfx] " Tvrtko Ursulin
2019-11-28 16:19 ` Chris Wilson
2019-11-28 16:19   ` [Intel-gfx] " Chris Wilson
2019-11-28 16:22   ` Chris Wilson
2019-11-28 16:22     ` [Intel-gfx] " Chris Wilson
2019-11-28 17:23     ` Tvrtko Ursulin
2019-11-28 17:23       ` [Intel-gfx] " Tvrtko Ursulin
2019-11-29 10:54   ` [PATCH v2] " Tvrtko Ursulin
2019-11-29 10:54     ` [Intel-gfx] " Tvrtko Ursulin
2019-12-06 12:32     ` Chris Wilson
2019-12-06 13:04       ` Tvrtko Ursulin [this message]
2019-12-06 12:33     ` Chris Wilson
2019-11-28 19:26 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-11-28 19:26   ` [Intel-gfx] " Patchwork
2019-11-29 18:38 ` ✓ Fi.CI.BAT: success for drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) Patchwork
2019-11-29 18:38   ` [Intel-gfx] " Patchwork
2019-11-30 17:52 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-11-30 17:52   ` [Intel-gfx] " 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=9804a5e4-efad-1746-91f9-a327ccb55dfd@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    /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