ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Kevin Hilman <khilman@kernel.org>
Cc: "Brown, Len" <len.brown@intel.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Kristen Carlson Accardi <kristen@linux.intel.com>,
	Grant Likely <grant.likely@linaro.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] System-wide interface to specify the level of PM tuning
Date: Sun, 12 Jul 2015 12:01:27 +0200	[thread overview]
Message-ID: <CAKMK7uHH=YdktPHMWoo21YEHP8jB_A-369GpYU5syi-a0idPaw@mail.gmail.com> (raw)
In-Reply-To: <7hlheo9b7m.fsf@deeprootsystems.com>

On Fri, Jul 10, 2015 at 7:25 PM, Kevin Hilman <khilman@kernel.org> wrote:
> "Rafael J. Wysocki" <rjw@rjwysocki.net> writes:
>
>> On Monday, July 06, 2015 01:49:45 PM Iyer, Sundar wrote:
>
> [...]
>
>>> Is a "single setting somewhere" even appropriate? It is actually the intelligence
>>> needed vs executing the actions?
>>
>> For one example, the default for most of the device/.../power/control files in
>> sysfs is "on" (meaning no runtime PM) while it might be "auto" (use runtime PM
>> if you can).  Making that change for everybody in one go may lead to various
>> issues (that may be regarded as regressions then), but if we made it configurable,
>> people might choose to make that change for themselves if they wanted to.
>
> I'd be very supportive of some default knob (or cmdline option) to favor
> energy efficiency.  For runtime PM, I suspect the resulting performance
> regressions are mostly (relatively) simple fixes, like enabling
> autosuspend, etc.
>
> Also, having a system-wide way to enable this mode would also enable us
> to find/report these bugs/regressions in a way that would be easily
> repeatable.  With the current pile of knobs/tunables, it's often very
> hard to reproduce problems others may be seeing.

My approach in drm/i915 is that there's just one default config and
that's the well-tuned one. Maybe gfx is special, but with todays
power-envelope constrained chips it's not a question of performance
_or_ power efficiency, but always _and_: Enabling power saving
features improves performance. And where it doesn't we just fix those
problems with smarter code (since usually the performance regressions
happen when you ping-pong too badly between different levels, or are
stuck for too long in a given power saving level). The other reason
for that approach is that gfx is complex and we just can't test
arbitrary combinations of options - hence we auto-taint the kernel if
users touch anything at all.

The downside is that you'll get more bug reports and can't hide from
them easily ;-)

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2015-07-12 10:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06  0:22 Rafael J. Wysocki
2015-07-06  1:21 ` Josh Triplett
2015-07-06 14:04   ` Rafael J. Wysocki
2015-07-06  1:40 ` NeilBrown
2015-07-06 14:12   ` Rafael J. Wysocki
2015-07-06 13:49     ` Iyer, Sundar
2015-07-06 14:21       ` Rafael J. Wysocki
2015-07-07  7:53         ` Jiri Kosina
2015-07-07 12:33           ` Rafael J. Wysocki
2015-07-10 17:25         ` Kevin Hilman
2015-07-12 10:01           ` Daniel Vetter [this message]
2015-07-13 23:07             ` Rafael J. Wysocki
2015-07-14 16:51               ` Daniel Vetter
2015-07-15 22:44                 ` Rafael J. Wysocki
2015-07-16  1:10                   ` Josh Triplett
2015-07-16  9:19                     ` David Woodhouse
2015-07-16 15:44                       ` Kristen Accardi
2015-07-16 15:53                         ` Josh Triplett
2015-07-16 15:58                           ` Greg KH
2015-07-17 10:34                             ` Takashi Iwai
2015-07-17 11:41                             ` Daniel Vetter
2015-07-20 22:21                               ` Rafael J. Wysocki
2015-07-20 23:09                                 ` Daniel Vetter
2015-07-22  1:12                                   ` Rafael J. Wysocki
2015-07-22  7:18                                     ` Daniel Vetter
2015-07-22 17:25                                       ` Rafael J. Wysocki
2015-07-22 18:25                                         ` josh
2015-07-24 22:36                                           ` Rafael J. Wysocki
2015-07-25 19:50                                             ` Josh Triplett
2015-07-26  0:03                                               ` Rafael J. Wysocki
2015-07-26  0:16                                                 ` Josh Triplett
2015-07-27 13:30                                                   ` Rafael J. Wysocki
2015-07-27 11:50                                               ` Jani Nikula
2015-07-06 16:33     ` Kristen Accardi

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='CAKMK7uHH=YdktPHMWoo21YEHP8jB_A-369GpYU5syi-a0idPaw@mail.gmail.com' \
    --to=daniel.vetter@ffwll.ch \
    --cc=grant.likely@linaro.org \
    --cc=khilman@kernel.org \
    --cc=kristen@linux.intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=len.brown@intel.com \
    --cc=stern@rowland.harvard.edu \
    /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