From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
Date: Fri, 02 May 2014 23:42:23 +0000 [thread overview]
Message-ID: <bug-75121-12968-E3POZEH6v0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75121-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75121
--- Comment #6 from Doug Smythies <dsmythies@telus.net> ---
Created attachment 134771
--> https://bugzilla.kernel.org/attachment.cgi?id=134771&action=edit
output from perf script as requested
I had troubles with phoronix stuff also when I tried to run it under "perf
record". It seemed to think it needed to re-install and then I couldn't find
where the test profile was, so that I could change it to 1 run instead of the
default 3 (I typically run it 10 times, and always abort the first run because
it has an inconsistent run time due to the extra time needed to load the file,
which thereafter is cached).
In the end I ran this:
sudo /home/doug/bin/perf record -a -c 1 -e power:pstate_sample
phoronix-test-suite benchmark pts/ffmpeg
The output from "pref script" has been truncated to just one of the 3 tests.
Myself, I find it much easier to interpret pref data captured for the "consume"
program that was used to make the other graphs. I'll attach some of that data
also.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-05-02 23:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 23:47 [Bug 75121] New: Intel Pstate driver - powersave mode - CPU frequency too low bugzilla-daemon
2014-04-29 23:54 ` [Bug 75121] " bugzilla-daemon
2014-04-29 23:56 ` bugzilla-daemon
2014-04-29 23:59 ` bugzilla-daemon
2014-04-30 0:08 ` bugzilla-daemon
2014-05-02 14:25 ` bugzilla-daemon
2014-05-02 23:42 ` bugzilla-daemon [this message]
2014-05-02 23:58 ` bugzilla-daemon
2014-05-03 0:03 ` bugzilla-daemon
2014-05-03 0:05 ` bugzilla-daemon
2014-05-03 0:11 ` bugzilla-daemon
2014-05-03 0:19 ` bugzilla-daemon
2014-05-03 0:47 ` bugzilla-daemon
2014-05-03 0:47 ` bugzilla-daemon
2014-05-03 3:49 ` bugzilla-daemon
2014-05-03 3:58 ` bugzilla-daemon
2014-05-03 4:59 ` bugzilla-daemon
2014-05-03 5:00 ` bugzilla-daemon
2014-05-04 19:18 ` bugzilla-daemon
2014-05-05 18:05 ` bugzilla-daemon
2014-05-05 18:52 ` bugzilla-daemon
2014-05-08 22:19 ` bugzilla-daemon
2014-05-08 22:21 ` bugzilla-daemon
2014-05-08 22:26 ` bugzilla-daemon
2014-05-28 21:22 ` bugzilla-daemon
2014-06-03 20:45 ` bugzilla-daemon
2015-07-21 19:28 ` 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-75121-12968-E3POZEH6v0@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.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).