From: Thomas Renninger <trenn@suse.de>
To: "Petr Šabata" <contyk@redhat.com>
Cc: Rainer Maier <RaMaier@gmx.de>, cpufreq@vger.kernel.org
Subject: Re: Fehler bei cpufreq-info
Date: Fri, 05 Apr 2013 16:01:20 +0200 [thread overview]
Message-ID: <2017362.3fkGx2zPkK@skinner.arch.suse.de> (raw)
In-Reply-To: <20130403075303.GA24986@rincewind.usersys.redhat.com>
On Wednesday, April 03, 2013 09:53:04 AM Petr Å abata wrote:
> On Tue, Apr 02, 2013 at 11:29:23PM +0200, Rainer Maier wrote:
> > Hi Thomas,
> > thanks for your info.
> > I removed cpufrequtils, but when I tried to install cpupower by aptitude
> > it didn't know the package. I searched for it, but couldn't find one.
> > Would you perhaps know which packet to install ?
> >
> > Thanks
> > Rainer
>
> The cpupower utilities are part of the kernel tree now and
> included in the kernel-tools package on Fedora. I suppose it
> will be something similar in your distribution.
Sigh.
I guess you have a separate perf package at least?
It would be great if cpupower gets packaged separately for two
reasons:
1) cpuidle and cpufreq are used by a lot archs nowadays:
ppc, arm, afaik S390 at least they tried,...
I expect the kernel-tools package will only compile on X86?
2) To avoid confusion like above, so that this tool can easily
be found by people searching for it.
Petr: Would you mind forward this to the maintainer.
I once made sure cpupower compiles on ppc iirc, if someone
runs into arch specific compile (or runtime) issues, please let
me know, this should get fixed then.
Thanks,
Thomas
Rainer: Again, if you have any cpufreq related problems it's probably
to p4-clockmod which is not a real cpufreq driver. The technique used
should only be used to avoid critical cpu temperature and does not
save you power, more the other way around (things should be processed
quickly so that CPU sleep states can be entered which are most efficient).
It even can be that p4-clockmode interferes with another interface doing
the same (CPU throttling, T-states) then your system becomes even more
laggy up to unusable.
next prev parent reply other threads:[~2013-04-05 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 12:53 Fehler bei cpufreq-info Rainer Maier
2013-03-29 13:47 ` Viresh Kumar
2013-04-02 8:42 ` Thomas Renninger
2013-04-02 21:29 ` Rainer Maier
2013-04-03 7:53 ` Petr Šabata
2013-04-05 14:01 ` Thomas Renninger [this message]
2013-04-05 14:31 ` Petr Šabata
2013-04-05 15:04 ` Thomas Renninger
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=2017362.3fkGx2zPkK@skinner.arch.suse.de \
--to=trenn@suse.de \
--cc=RaMaier@gmx.de \
--cc=contyk@redhat.com \
--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