From: Jason Brittain <jason@brittainweb.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu vs Standard
Date: Tue, 15 Feb 2005 12:59:29 -0800 [thread overview]
Message-ID: <421262B1.2080502@brittainweb.org> (raw)
In-Reply-To: <aec7e5c3050215120571875355@mail.gmail.com>
Magnus Damm wrote:
>>
>>Interesting! I wrote the email about all this while riding to work on
>>the subway. So, when I did the "cat /proc/cpuinfo", I was indeed running
>>on battery power. But, currently, I'm not, and still says the same thing.
>>
>>Anyone know what the deal is with that? Is that an accurate number
>>saying that my cpu is throttled down? Could I make it run faster then?
>>Hmmmm..
>
> On a 2.6-kernel with cpufreq enabled, have a look at the files in
> "/sys/devices/system/cpu/cpu0/cpufreq/". Try to echo "powersave" or
> "performance" to scaling_governor. Then look at "/proc/cpuinfo" to see
> the actual MHz.
Ahh, yeah. I did:
# echo "performance" >> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
And now my /proc/cpuinfo looks like:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.80GHz
stepping : 6
cpu MHz : 1799.038
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe est tm2
bogomips : 3563.52
BUT, I retried my tests and the performance numbers/timings came out the same.
> You can also play around with acpi throttling in
> "/proc/acpi/processor/*/throttling". I guess * should be replaced with
> CPU0, but on my crappy laptop with wierd acpi info CPU1 must be used
> instead of CPU0.
>
> Also, try cpufreqd or cpudyn to adjust the cpu frequency on the fly.
Thanks for the tips on those. I'll look into them.
Darryl Dixon wrote:
> That's just the natural effect of the Speedstep technology throttling
> back the cpu to lower heat because you aren't using many cpu cycles at
> the moment (you aren't pushing your laptop very hard :). If you were to
> do something like, say, compile Wine, and while it is compiling cat
> /proc/cpuinfo, you would see that the speed is up at 1800MHz.
I believe this, since the CPU performance turned out the same either way.
More good info.. thanks!
--
Jason Brittain
next prev parent reply other threads:[~2005-02-15 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 17:55 [Qemu-devel] kqemu vs Standard Jason Brittain
2005-02-15 18:28 ` Karel Gardas
2005-02-15 18:55 ` Jason Brittain
2005-02-15 19:43 ` Thomas Petazzoni
2005-02-15 20:05 ` Magnus Damm
2005-02-15 20:59 ` Jason Brittain [this message]
2005-02-15 20:18 ` Darryl Dixon
2005-02-15 19:43 ` James Mastros
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=421262B1.2080502@brittainweb.org \
--to=jason@brittainweb.org \
--cc=qemu-devel@nongnu.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).