From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Josh Triplett <josh@joshtriplett.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: Mon, 27 Jul 2015 15:30:24 +0200 [thread overview]
Message-ID: <1591143.F5lcGfdGXX@vostro.rjw.lan> (raw)
In-Reply-To: <20150726001600.GA19810@x>
On Saturday, July 25, 2015 05:16:00 PM Josh Triplett wrote:
> On Sun, Jul 26, 2015 at 02:03:55AM +0200, Rafael J. Wysocki wrote:
> > On Saturday, July 25, 2015 12:50:16 PM Josh Triplett wrote:
[cut]
> >
> > Say the user has a new machine and doesn't know which tunables can be safely
> > enabled on it. The only way to check is to toggle all of them and see if
> > anything breaks. The difficulty here is that the user actually needs to
> > know about all of them which takes quite a bit of research and if nothing
> > breaks really that's a fair amount of work pretty much in vain. A global
> > switch would make it somewhat easier for the lucky users whose systems
> > don't break after toggling it.
>
> Odds are at least one thing will break, though, and if the user doesn't
> know about all of the tunables they just changed, they won't necessarily
> know how to diagnose the reason, especially if the failure is more
> subtle and doesn't completely break the system.
>
> Perhaps, as a start towards this, we could document all the "might or
> might not work" power management tunables in one place, and document
> what might go wrong if they don't work on your system. That could then
> easily become an /etc/sysctl.d file to toggle them all. And even if we
> offer a single global "dangerous PM tunables" switch, that document
> would help identify what might go wrong and help re-disable the things
> that don't work.
That sounds like a good idea to me.
Thanks,
Rafael
next prev parent reply other threads:[~2015-07-27 13:03 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
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 [this message]
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=1591143.F5lcGfdGXX@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=grant.likely@linaro.org \
--cc=josh@joshtriplett.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