qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joe Batt <Joe@soliddesign.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SMP support
Date: Tue, 22 Nov 2005 10:32:17 -0500	[thread overview]
Message-ID: <1132673537.2569.10.camel@fred.ofc.soliddesign.net> (raw)
In-Reply-To: <43825F9E.3050103@bellard.org>

This

	qemu -smp 2 -cdrom KNOPPIX_V3.8-2005-02-28-CeBIT_Edition-qemu-0.6.1-2.iso

fails, but work fine without the -smp flag.  The KNOPPIX has fairly
random seg faults.  I had similar results with 4 virutal cpus.

The host is a dual Xeon with hyperthreading turned on (so 4 total
"CPUs") running Debian testing, and a custom 2.6.13 kernel.  The
compiler is gcc 3.3.5.

You didn't offer up any description.  Will this take advantage of host
SMP?  How?  (Each of us could read the code, or you could save the
collective a bunch of time...)

Joe
 
On Tue, 2005-11-22 at 01:00 +0100, Fabrice Bellard wrote:
> Hi all,
> 
> I just commited the code to emulate SMP targets. As an example, I added 
> support for x86 PCs with up to 8 CPUs (option -smp).
> 
> There are still some optimisations to do regarding the scheduling and I 
> only tested the code with a Linux 2.4 guest OS.
> 
> Happy testing :-)
> 
> Fabrice.
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
-- 
Joe Batt <Joe@soliddesign.net>

  parent reply	other threads:[~2005-11-22 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22  0:00 [Qemu-devel] SMP support Fabrice Bellard
2005-11-22  4:19 ` Anthony Liguori
2005-11-22  4:46 ` Mulyadi Santosa
2005-11-22 15:32 ` Joe Batt [this message]
2005-11-22 19:23   ` Fabrice Bellard
  -- strict thread matches above, loose matches on Subject: below --
2012-09-25 12:57 Julio Guerra

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=1132673537.2569.10.camel@fred.ofc.soliddesign.net \
    --to=joe@soliddesign.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).