qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Speed menu for GTK interfaace
Date: Wed, 04 Jan 2017 09:37:39 +0100	[thread overview]
Message-ID: <1483519059.5670.42.camel@redhat.com> (raw)
In-Reply-To: <D2287F42-8073-421D-9920-3048D63B41E3@gmail.com>

  Hi,

> It is quite simple, there would be a 100% to a 1% menu item. It would look like
> this:
> 
> Speed
> -------
> 100%
> 90%
> 80%
> 70%
> 60%
> 50%
> 40%
> 30%
> 20%
> 10%
> 1%
> 
> 
> Each menu item would call cpu_throttle_set(). The value sent to this function would
> be determined like this:
> speed = -1 * menu_number + 100;

ok, that is the info I was looking for.

> speed would be sent to the cpu_throttle_set() function. This function would reduce
> the CPU usage of QEMU on the host. 
> 
> Why would someone want to slow down QEMU?
> - The user is using a laptop and don't want it to heat up.

Sort-of makes sense, to keep the laptop quiet.

> - The user wants to slow down a video game that is a little too challenging.

Sure this would work?  Throttling isn't a smooth slowdown, the cpu
continues to run at full speed and is forced to pause now and then.

> - The user wants to save energy.

Pointless.  Laptop may run longer, but your job needs more time to
complete too.  And constant vcpu start/stop isn't good to save power,
the cpus can't enter deep sleep states then because of the frequent
wakeups.

> - The user wants to conduct some kind of stress test on a program and see how
> it handles under low cpu resources. 

Makes sense too.

We already have "pause" in gtk, adding a "throttle" item next to it
looks reasonable to me.  I don't think it is that useful to have 10%
steps in there, you probably never throttle 10% in practice.  It's
probably more useful to have something like "throttle -> off / 50% /
90% / 95% / 99%".

cheers,
  Gerd

  reply	other threads:[~2017-01-04  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01 18:15 [Qemu-devel] Speed menu for GTK interfaace Programmingkid
2017-01-03  8:59 ` Gerd Hoffmann
2017-01-03 16:37   ` Programmingkid
2017-01-04  8:37     ` Gerd Hoffmann [this message]
2017-01-04 15:43       ` Programmingkid
2017-01-04 15:51       ` Daniel P. Berrange
2017-01-04 16:01         ` Programmingkid
2017-01-04 16:19           ` Daniel P. Berrange
2017-01-04 16:22             ` Programmingkid
2017-01-04 20:55         ` Gerd Hoffmann

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=1483519059.5670.42.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=programmingkidx@gmail.com \
    --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).