From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 206517] scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX
Date: Fri, 14 Feb 2020 08:02:47 +0000 [thread overview]
Message-ID: <bug-206517-137361-xlq1JVTple@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206517-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206517
Thomas Renninger (trenn@suse.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trenn@suse.de
--- Comment #1 from Thomas Renninger (trenn@suse.de) ---
Best use:
cpupower monitor
You can also measure workloads, e.g. when compiling something:
cpupower monitor make
Not sure what distro you are using and what the name of the package or whether
cpupower is packaged there... The sources, even it's userspace is part of the
kernel git repo:
tools/power/cpupower
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-02-14 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 15:27 [Bug 206517] New: scaling_cur_freq very different from cpuinfo_cur_freq on Acer Predator Helios 500 PH517-61-R0GX bugzilla-daemon
2020-02-14 8:02 ` bugzilla-daemon [this message]
2020-06-29 12:16 ` [Bug 206517] " bugzilla-daemon
2020-06-29 12:17 ` 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-206517-137361-xlq1JVTple@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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).