qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Fabrice Bellard <fabrice.bellard@free.fr>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Snapshot block device support
Date: Mon, 07 Jul 2003 18:15:57 +1000	[thread overview]
Message-ID: <20030707081644.EA7D92C0EA@lists.samba.org> (raw)
In-Reply-To: Your message of "Sun, 06 Jul 2003 16:08:13 +0200." <3F082D4D.6010505@free.fr>

In message <3F082D4D.6010505@free.fr> you write:
> > Even with only one CPU, it helps my debugging to be able to test
> > CONFIG_SMP=y...
> 
> I realize that SMP simulation can be interesting. I could at least learn 
> how it works as I never looked at it. The simplest solution would be to 
> use CONFIG_QEMU to change the FIXADDR_TOP address in fixmap.h (I am 
> going to test that). I have looked at APIC and IOAPIC simulation in 
> bochs and it does not seem so complicated. My real problem is how to 
> simulate several CPUs at the same time. A solution is to use a single 
> process and to schedule by hand. It is costly because the address space 
> must be switched between each CPU. Another solution is to use separate 
> processes, but it complicates the hardware simulation. Any ideas ?

I'd be happy for the moment with a single CPU, as long as an
CONFIG_SMP=y kernel booted.

I don't want to discourge you though!  If you were going to actually
simulate multiple CPUS, ideal would be one thread per cpu (which takes
advantage of an SMP host).  Switching simply doesn't exercise the race
conditions as much as an SMP host does.  I remember TDB bugs where
tdbtorture (multiprocess stress test) passed fine on UP, but blew up
every time on SMP.

Cheers!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-07-07  8:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02  6:50 [Qemu-devel] [PATCH] Snapshot block device support Rusty Russell
2003-07-02  9:49 ` [Qemu-devel] " Fabrice Bellard
2003-07-02 10:04   ` Thomas Glanzmann
2003-07-02 23:54   ` Rusty Russell
2003-07-04 14:51     ` Fabrice Bellard
2003-07-06  2:26       ` Rusty Russell
2003-07-06 14:08         ` Fabrice Bellard
2003-07-07  8:15           ` Rusty Russell [this message]
2003-07-07 12:51             ` 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=20030707081644.EA7D92C0EA@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=fabrice.bellard@free.fr \
    --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).