From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Qemu-devel Digest, Vol 22, Issue 46
Date: Fri, 21 Jan 2005 22:23:33 +0000 [thread overview]
Message-ID: <200501212223.34603.paul@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0501212025510.2013-100000@jdesk.thechesterfields.org>
On Friday 21 January 2005 20:53, Julian Chesterfield wrote:
> >It shouldn't make a different if the host OS
> >uses it
> >or not.
>
> Excuse my ignorance but is this because there is no
> potential for parallelising tasks in qemu to take advantage of idle
> CPU cycles?
In theory you could put CPU and system emulation in separate threads. In
practice I suspect the synchronisation overhead outweighs the (small) benefit
that hyperthreading gives you. I'm not even sure it's give any significant
benefit on real SMP systems.
Simulating multiple cpu SMP guest system on a SMP host cpus would be
interesting, but that's a whole new thing.
Paul
next prev parent reply other threads:[~2005-01-21 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501212010.j0LKA1XT001930@jdesk.thechesterfields.org>
2005-01-21 20:53 ` [Qemu-devel] Re: Qemu-devel Digest, Vol 22, Issue 46 Julian Chesterfield
2005-01-21 21:59 ` Jim C. Brown
2005-01-21 22:23 ` Paul Brook [this message]
2005-01-21 23:09 ` Fabrice Bellard
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=200501212223.34603.paul@codesourcery.com \
--to=paul@codesourcery.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).