From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: TransMeta longrun control utility maintainer?
Date: 6 Mar 2003 12:11:31 -0800 [thread overview]
Message-ID: <b48a1j$4tu$1@cesium.transmeta.com> (raw)
In-Reply-To: 9cfy93s4mbd.fsf@rogue.ncsl.nist.gov
Followup to: <9cfy93s4mbd.fsf@rogue.ncsl.nist.gov>
By author: Ian Soboroff <ian.soboroff@nist.gov>
In newsgroup: linux.dev.kernel
>
> I know this isn't the best place to ask, but maybe someone here knows.
>
> Who is maintaining the longrun(1) (should probably be longrun(8))
> utility? The author is listed as Daniel Quinlan
> <quinlan@transmeta.com>, but mail to that address bounces.
>
> The longrun utility frobs the MSR on TransMeta processors to switch
> between performance and economy modes.
>
> On my laptop, currently running 2.4.21-pre5-ac1, I get the following
> error:
>
> # longrun -p
> longrun: error reading /dev/cpu/0/cpuid: Invalid argument
>
> # ls -l /dev/cpu/0
> total 0
> cr--r--r-- 1 root root 203, 0 Aug 30 2002 cpuid
> crw------- 1 root root 10, 184 Aug 30 2002 microcode
> crw------- 1 root root 202, 0 Aug 30 2002 msr
>
Compile with -D_FILE_OFFSET_BITS=64 and it should work. The problem
is that some of the MSRs and CPUID levels it touches have addresses
above 0x80000000, and newer glibc's running on newer kernels interpret
those as 64-bit negative, i.e. 0xffffffff80000000.
The longrun utility is currently unmaintained (and Longrun control is
being integrated into the cpufreq framework), but I can at least take
minor bug reports.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
prev parent reply other threads:[~2003-03-06 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 14:11 TransMeta longrun control utility maintainer? Ian Soboroff
2003-03-06 18:18 ` Greg KH
2003-03-10 15:07 ` Ian Soboroff
2003-03-06 20:11 ` H. Peter Anvin [this message]
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='b48a1j$4tu$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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