From: "Jamie Burns" <jamie.burns@dynamicexpression.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu workstation
Date: Tue, 6 Apr 2004 15:00:23 +0100 [thread overview]
Message-ID: <001901c41bdf$81ce3b90$6407a8c0@shaggy> (raw)
In-Reply-To: 20040406121738.GC2774@linux-m68k.org
Isnt there an instruction that gets sent when the OS is idle? To keep
processors cool etc?
VMWare describes some of this in:
http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1077
:o)
----- Original Message -----
From: "Richard Zidlicky" <rz@linux-m68k.org>
To: <qemu-devel@nongnu.org>
Sent: Tuesday, April 06, 2004 1:17 PM
Subject: Re: [Qemu-devel] Qemu workstation
> On Mon, Apr 05, 2004 at 10:49:51PM +0100, Jamie Burns wrote:
> > > I am not sure that handling multiple VMs running at the same time is
> > > very useful (some architectural changes are needed in QEMU). But
> > > switching easily between VM configurations seems interesting.
> >
> > I think that multiple VM's is a worthy goal as long as you can minimise
CPU
> > usage. Having multiple VM's gives you the ability to do some very cool
> > things. I use VMWARE in Windows and sometimes have both Linux and
FreeBSD
> > running in VM's so I can test software against all 3 OS's at once. I
imagine
> > it would be very useful to developers of cluster software.
> >
> > I tried the Win32 port the other day, running Linux, and it sat using
100%
> > of the CPU whilst doing next to nothing at a command prompt. Using
VMWARE,
> > and waiting at a command prompt uses very little CPU time.
> >
> > Is QEMU sat in a busy loop all the time?
>
> it is not QEMU but the hosted OS that is in the busy loop. QEMU
> will have to recognise "idle loops" to fix this - this could be
> really tricky.
>
> Richard
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-04-06 14:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 8:47 [Qemu-devel] Qemu workstation Jean-Michel POURE
2004-04-05 9:10 ` John R. Hogerhuis
2004-04-05 9:30 ` Rudi Lippert
2004-04-05 9:55 ` Jean-Michel POURE
2004-04-05 19:31 ` Fabrice Bellard
2004-04-05 21:49 ` Jamie Burns
2004-04-06 12:17 ` Richard Zidlicky
2004-04-06 13:28 ` Brad Campbell
2004-04-06 20:23 ` Filip Navara
2004-04-07 4:34 ` Brad Campbell
2004-04-07 7:59 ` Filip Navara
2004-04-07 8:24 ` Brad Campbell
2004-04-07 8:47 ` Grzegorz Kulewski
2004-04-07 17:50 ` Richard Zidlicky
2004-04-07 9:40 ` Filip Navara
2004-04-06 14:00 ` Jamie Burns [this message]
2004-04-06 19:00 ` Fabrice Bellard
2004-04-05 9:38 ` Jean-Michel POURE
2004-04-05 10:23 ` John R. Hogerhuis
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 15:19 Mike Nordell
2004-04-05 20:40 ` Filip Navara
2004-04-05 21:05 ` John R. Hogerhuis
2004-04-05 21:15 ` Filip Navara
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='001901c41bdf$81ce3b90$6407a8c0@shaggy' \
--to=jamie.burns@dynamicexpression.co.uk \
--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).