linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 00:40:53 +0000	[thread overview]
Message-ID: <bug-194963-137361-zooxmJmNr7@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 #6 from John (john.ettedgui@gmail.com) ---
The schedutil patch didn't seem to change anything, though the 4th hunk of
cpufreq_schedutil.c didn't apply and I had to do it manually, so it is possible
I messed up somewhere (I copied/pasted it so it's unlikely, but I thought it'd
be better to say it).

As for pstate, I think that's the first time I've seen my CPU scaling on
pstate's powersave. I've tried the game, and I think, but not sure, that when
it started the sound cracked for just a bit, maybe before the CPU scaled up
enough? After that no issue, and I verified the CPU was at its maximum
frequency. When I quit the game, the CPU scaled down to its minimum frequency
within 2 seconds. Pstate's performance still doesn't scale, is it expected? I
thought on pstate both would.

Thank you!

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2017-03-24  0:52 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 [this message]
2017-03-24  1:11 ` bugzilla-daemon
2017-03-24  4:02 ` bugzilla-daemon
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-zooxmJmNr7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).