All of lore.kernel.org
 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: Thu, 23 Mar 2017 23:03:36 +0000	[thread overview]
Message-ID: <bug-194963-137361-1kaQ6Xu4BG@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 #4 from John (john.ettedgui@gmail.com) ---
(In reply to Viresh Kumar from comment #2)
> John,
> 
> Can you please give us the value of 
> /sys/devices/system/cpu/cpufreq/schedutil/rate_limit_us
> 
> ?
> 
> Try making this around 10000 (10ms). This is how frequently we try to change
> the frequency and lowering it will make us more aggressive.

Hello Viresh,

cat /sys/devices/system/cpu/cpufreq/schedutil/rate_limit_us
10000

It's already at that value, are there others you'd like me to try?

(In reply to Rafael J. Wysocki from comment #3)
> It also would be good to test this patch:
> 
> https://patchwork.kernel.org/patch/9637821/
> 
> and maybe also this one:
> 
> https://patchwork.kernel.org/patch/9640261/
> 
> to see if it improves things for the intel_pstate "powersave" on that
> machine.

Hello Rafael,

I will try these and report.
Does it matter if I use both patches together?


Thank you!

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

  parent reply	other threads:[~2017-03-23 23:03 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 [this message]
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
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-1kaQ6Xu4BG@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.