From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 194963] schedutil governor causes audio problem in game
Date: Fri, 24 Mar 2017 04:02:21 +0000 [thread overview]
Message-ID: <bug-194963-137361-0ezpm8lLZ8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194963-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194963
--- Comment #8 from John (john.ettedgui@gmail.com) ---
(In reply to Rafael J. Wysocki from comment #7)
> OK, this means that schedutil is not a good match for you.
>
> It is a bit less aggressive than ondemand, on purpose.
Oh I see, I didn't realize that, I thought it was about as dynamic as ondemand.
Then I am sorry about a wrong report!
> There is one more schedutil change that you may try, but I need to prepare a
> patch for that first.
>
I'll be happy to test it whenever it's ready. Since I have plenty of workaround
there's of course no sense of urgence on my end.
> If you mean scaling_governor=performance, then it will always request the
> max P-state now, as that's what it is supposed to be doing.
Yes that is what I meant, I thought scaling_governor=performance with
driver=intel_pstate would scale unlike with driver=cpufreq, I was wrong again.
> Thanks for the testing, the intel_pstate change will be queued up for 4.12
> in the next couple of days.
Well thank you for this patch, I am happy to finally be able to use pstate :)
If you don't mind me asking here, since we talked about many different
governors, and their drivers, which one do you recommend for a desktop, that
does run games, but also other things that don't require much power. Based on
my tests I'm thinking either cpufreq's ondemand or pstate's powersave.
Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-03-24 4:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 10:40 [Bug 194963] New: schedutil governor causes audio problem in game bugzilla-daemon
2017-03-23 13:07 ` [Bug 194963] " bugzilla-daemon
2017-03-23 14:31 ` bugzilla-daemon
2017-03-23 15:11 ` bugzilla-daemon
2017-03-23 23:03 ` bugzilla-daemon
2017-03-23 23:23 ` bugzilla-daemon
2017-03-24 0:40 ` bugzilla-daemon
2017-03-24 1:11 ` bugzilla-daemon
2017-03-24 4:02 ` bugzilla-daemon [this message]
2017-03-24 15:17 ` bugzilla-daemon
2017-03-24 23:06 ` bugzilla-daemon
2017-03-27 23:12 ` bugzilla-daemon
2017-03-27 23:14 ` bugzilla-daemon
2017-03-28 22:54 ` bugzilla-daemon
2017-03-29 0:28 ` bugzilla-daemon
2017-03-29 5:21 ` bugzilla-daemon
2017-03-29 6:27 ` bugzilla-daemon
2017-03-29 20:28 ` bugzilla-daemon
2017-03-30 3:32 ` bugzilla-daemon
2017-03-30 14:24 ` bugzilla-daemon
2017-03-31 3:51 ` bugzilla-daemon
2017-03-31 8:45 ` bugzilla-daemon
2017-03-31 8:57 ` bugzilla-daemon
2017-03-31 9:00 ` bugzilla-daemon
2017-05-07 14:58 ` bugzilla-daemon
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=bug-194963-137361-0ezpm8lLZ8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.