From: "Salonie, Namrta" <namrta.salonie@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Enabling RC6 immediately during init/resume
Date: Mon, 31 Aug 2015 17:08:36 +0530 [thread overview]
Message-ID: <55E43CBC.5060103@intel.com> (raw)
In-Reply-To: <20150825143205.GJ20434@phenom.ffwll.local>
Hi Chris, Daniel.
Thanks for your inputs.
I agree that we need to amend the patch. Will do following changes.
1. RPM ref count is not needed with immediate enabling of RC6, I will
remove that.
2. I will extend this to other GEN as well.
This was one of the set of optimization we implemented for BYT Android.
All of these
gave improvement of ~5mW for 30minutes for Active Idle WLAN KPI. And
about ~5mW for other airplane, wifi, radio suspend scenarios.
The other optimizations included :-
1. Reduction of autosuspend delay to 500ms from 10ms (On BYT, display D3
should happen in suspend as Punit initiates S0iX flow only considering
Display D3). Because of this reduction Display D3 will happen
immediately: This can be controlled by user mode in android. However
shall we bring this value for Linux as well?
2. Deferring RC6 disabling from early_resume callback to resume callback
to reduce the delay for which the wells had to stay ON – We verified the
HDMI case and it worked without issues.
3. During resume, perform modeset based on the DPMS state, so that
Display remains Off for the intermediate wake ups where no DPMS ON/OFF
happens.
Also, can we port the optimizations 2 & 3 to the upstream kernel?
Thanks,
Namrta
On 8/25/2015 8:02 PM, Daniel Vetter wrote:
> On Fri, Aug 21, 2015 at 01:41:26PM +0100, Chris Wilson wrote:
>> On Sat, Aug 22, 2015 at 02:19:48AM +0530, Namrta Salonie wrote:
>>> Since RC6 enabling does not involve PCU communication overhead,
>>> it can be enabled immediately during the resume time.
>>> This will help save additional power & meet power requirements
>>> for active Idle KPI where power is evaluated over
>>> number of transitions of suspend/resume.
>>>
>>> Signed-off-by: Namrta Salonie <namrta.salonie@intel.com>
>>> Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
>>
>> You can pull out gen9 rc6 as well, and apply a similar transformation to
>> gen6-8. So instead of putting the if-chain in
>> intel_enable_gt_powersave(), add intel_enable_rc6() and start placing
>> the ready functions there.
>>
>> Reviewing the comments we only need the rpm lock until after rc6
>> enabling and as you keep that wakelock, you are not getting the full
>> improvement you seek. If you keep refactoring the remaining two rc6
>> functions, you can then drop the wakelock.
>
> Since this seems to not have much of a benefit due to the missing removal
> of the wakelock I wonder how this was tested ... Next patch should have
> (relative, we're not allowed to publish absolute) performance data
> attached, e.g. "Over 100 suspend/resume cycles with 5s of idle time in
> between each suspend/resume time this reduce in a reduction of $number
> $unit."
>
> Without this this patch is just unjustified tuning and I won't take it.
> -Daniel
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-31 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 20:49 [PATCH] drm/i915: Enabling RC6 immediately during init/resume Namrta Salonie
2015-08-21 12:41 ` Chris Wilson
2015-08-25 14:32 ` Daniel Vetter
2015-08-31 11:38 ` Salonie, Namrta [this message]
2015-09-02 8:30 ` Daniel Vetter
2015-12-02 5:45 ` Namrta Salonie
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=55E43CBC.5060103@intel.com \
--to=namrta.salonie@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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