From: "Petr Šabata" <contyk@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Rainer Maier <RaMaier@gmx.de>, cpufreq@vger.kernel.org
Subject: Re: Fehler bei cpufreq-info
Date: Fri, 5 Apr 2013 16:31:09 +0200 [thread overview]
Message-ID: <20130405143109.GA1451@noon.brq.redhat.com> (raw)
In-Reply-To: <2017362.3fkGx2zPkK@skinner.arch.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
On Fri, Apr 05, 2013 at 04:01:20PM +0200, Thomas Renninger wrote:
> 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?
Yes, but technically it's a kernel subpackage.
> 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?
They used to be a separate package before the code moved
to kernel. I see the package is build for ppc[64] but not
on s390[x]. I have no information on arm[64] at the moment
but if there are issues, I'll let you know :)
> 2) To avoid confusion like above, so that this tool can easily
> be found by people searching for it.
This is handled by package manager. Besides the list of of
binaries the tools package should also act as a replacement
for former cpufrequtils and cpupowerutils packages.
> 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.
See above.
I'll forward this to kernel owners in Fedora.
Regards,
Petr
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2013-04-05 14:31 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
2013-04-05 14:31 ` Petr Šabata [this message]
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=20130405143109.GA1451@noon.brq.redhat.com \
--to=contyk@redhat.com \
--cc=RaMaier@gmx.de \
--cc=cpufreq@vger.kernel.org \
--cc=trenn@suse.de \
/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