From: Viresh Kumar <viresh.kumar@linaro.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Zhang Rui <rui.zhang@intel.com>,
daniel.lezcano@linaro.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, rjw@rjwysocki.net,
linux-pm@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, x86@kernel.org
Subject: Re: 5.2-rc2: low framerate in flightgear, cpu not running at full speed, thermal related?
Date: Tue, 11 Jun 2019 15:45:17 +0530 [thread overview]
Message-ID: <20190611101517.jen4bbiyqzdz4f2r@vireshk-i7> (raw)
In-Reply-To: <20190611101213.GA4256@amd>
On 11-06-19, 12:12, Pavel Machek wrote:
> v5.2:
> pavel@duo:~$ cat /sys/devices/system/cpu/*/cpufreq/scaling_governor
> powersave
> powersave
> powersave
> powersave
>
> v4.6:
>
> pavel@duo:~$ cat /sys/devices/system/cpu/*/cpufreq/scaling_governor
> ondemand
> ondemand
> ondemand
> ondemand
Hmm, the governors are different. But powersave should have picked the
lowest frequency always.
What about cpufreq driver ?
cat /sys/devices/system/cpu/*/cpufreq/scaling_driver
--
viresh
next prev parent reply other threads:[~2019-06-11 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 11:17 5.2-rc2: low framerate in flightgear, cpu not running at full speed, thermal related? Pavel Machek
2019-06-09 11:23 ` Pavel Machek
2019-06-09 12:12 ` Pavel Machek
2019-06-09 13:55 ` Daniel Lezcano
2019-06-09 14:13 ` Zhang Rui
2019-06-11 10:12 ` Pavel Machek
2019-06-11 10:15 ` Viresh Kumar [this message]
2019-06-12 2:37 ` Doug Smythies
2019-06-12 21:44 ` Rafael J. Wysocki
2019-06-12 23:39 ` Doug Smythies
2019-06-13 8:11 ` Pavel Machek
2019-06-13 9:00 ` Rafael J. Wysocki
2019-06-13 8:52 ` Rafael J. Wysocki
2019-06-18 8:20 ` Doug Smythies
2019-06-18 8:34 ` Pavel Machek
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=20190611101517.jen4bbiyqzdz4f2r@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bp@alien8.de \
--cc=daniel.lezcano@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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).