From: "Kamble, Sagar A" <sagar.a.kamble@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"Szwichtenberg, Radoslaw" <radoslaw.szwichtenberg@intel.com>,
"S, Deepak" <deepak.s@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
"Goel, Akash" <akash.goel@intel.com>
Subject: Re: Why idle_freq is set to RPn and not RPe
Date: Thu, 31 Dec 2015 23:08:17 +0530 [thread overview]
Message-ID: <56856809.4080604@intel.com> (raw)
In-Reply-To: <20151230105016.GW31221@nuc-i3427.alporthouse.com>
On 12/30/2015 4:20 PM, Chris Wilson wrote:
> On Wed, Dec 30, 2015 at 04:09:46PM +0530, Kamble, Sagar A wrote:
>> Turbo frequency range is Rpe to Rp0 when GPU is active as, on workload
>> submission frequency is taken to Rpe.
>>
>> Does the HW require us to drop to RPn before entering RC6?
>> If we can enter RC6 even with other frequencies I think we can keep
>> running at Rpe on Idle.
> Remember that we quite frequently prevent the hardware going into RC6,
I assume this is threshold times in TO/EI mode for which GT is idle but
not power gated.
> and that it has been known for the hardware to fail to enter RC6 itself
> (through driver error or whatnot).
And assume this is because of forcewake/rc6 setup errors in driver paths
which should not happen in best case :)
Agree that running at Rpn makes sense.
> Going to the extreme, why wouldn't
> you set Rp0 on idle, since that will give the best restart latency?
True. We can have different logic that starts from Rp0 and comes down if
perf is met.
> -Chris
>
Thanks for the inputs Chris.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-31 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 9:21 Why idle_freq is set to RPn and not RPe Kamble, Sagar A
2015-12-30 9:31 ` Chris Wilson
2015-12-30 9:50 ` Szwichtenberg, Radoslaw
2015-12-30 10:00 ` Chris Wilson
2015-12-30 10:39 ` Kamble, Sagar A
2015-12-30 10:50 ` Chris Wilson
2015-12-31 17:38 ` Kamble, Sagar A [this message]
2016-01-05 16:51 ` Szwichtenberg, Radoslaw
2016-01-05 20:54 ` Chris Wilson
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=56856809.4080604@intel.com \
--to=sagar.a.kamble@intel.com \
--cc=akash.goel@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=deepak.s@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=radoslaw.szwichtenberg@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