From: Fabrice Bellard <fabrice@bellard.org>
To: Blue Swirl <blueswir1@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: request : qemu-smp as target
Date: Sat, 14 May 2005 14:16:30 +0200 [thread overview]
Message-ID: <4285EC1E.4090904@bellard.org> (raw)
In-Reply-To: <BAY104-F21B3902A51A90415295094FF130@phx.gbl>
Blue Swirl wrote:
> Hi,
>
> The architecture used in sparc target (sun4m) supports SMP up to a
> maximum of 16 CPUs. At hardware emulation level (hw/*, target-sparc/*),
> it would be easy to add the missing interprocessor interrupts, per-CPU
> counters and atomic instructions. It would also be simple to add the
> prom functions for starting/stopping CPUs to Proll. Maybe some days'
> work in total.
>
> Higher level (vl.c, cpu-exec.c) could need more work. Maybe Fabrice can
> enlighten us?
SMP est definitely possible in QEMU - a few days of work are necessary
to add the missing generic support and an x86 implementation... but
currently I prefer to work an other topics.
Just for your information, some choices need to be made:
1) Do the CPUs share the same translation cache ?
2) The first implementation would use a cycle counter to schedule
between CPUs. Is it interesting to go further and to use a host thread
for each guest CPU at the expense of more locking overhead ?
Fabrice.
next prev parent reply other threads:[~2005-05-14 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 9:37 [Qemu-devel] Re: request : qemu-smp as target Blue Swirl
2005-05-14 11:31 ` Paul Brook
2005-05-14 15:22 ` Blue Swirl
2005-05-14 12:16 ` Fabrice Bellard [this message]
2005-05-14 13:11 ` Jonas Maebe
2005-05-14 14:46 ` Blue Swirl
2005-05-14 16:55 ` Joe Batt
2005-05-17 20:21 ` Paul Brook
2005-05-17 20:41 ` Joe Batt
2005-05-17 20:59 ` Paul Brook
2005-05-18 11:29 ` Mark Williamson
2005-05-18 21:19 ` Re[2]: " Igor Shmukler
2005-05-18 11:25 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 13:17 octane indice
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=4285EC1E.4090904@bellard.org \
--to=fabrice@bellard.org \
--cc=blueswir1@hotmail.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).