qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu vs Standard
Date: Wed, 16 Feb 2005 09:18:46 +1300	[thread overview]
Message-ID: <1108498727.13207.2.camel@localhost.localdomain> (raw)
In-Reply-To: <421245A0.2080502@brittainweb.org>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

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.

Cheers,
D


On Tue, 2005-02-15 at 10:55 -0800, Jason Brittain wrote:

> Karel Gardas wrote:
> > On Tue, 15 Feb 2005, Jason Brittain wrote:
> > 
> >>Here's my real (laptop) hardware's CPU info:
> >># cat /proc/cpuinfo
> >>processor       : 0
> >>vendor_id       : GenuineIntel
> >>cpu family      : 6
> >>model           : 13
> >>model name      : Intel(R) Pentium(R) M processor 1.80GHz
> >>stepping        : 6
> >>cpu MHz         : 599.679
> > 
> > I just wonder, but do you usually work with CPU clocked-down? Or have you
> > tested running on battery?
> 
> 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..
> 

-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 2449 bytes --]

  parent reply	other threads:[~2005-02-15 20:54 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
2005-02-15 20:18     ` Darryl Dixon [this message]
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=1108498727.13207.2.camel@localhost.localdomain \
    --to=esrever_otua@pythonhacker.is-a-geek.net \
    --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).