From: Andreas <andreas.faerber@web.de>
To: 陳韋任 <chenwj@iis.sinica.edu.tw>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
Lluís <xscript@gmx.net>, "Greg McGary" <greg.mcgary@gmail.com>,
"qemu-devel Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Multi heterogenous CPU archs for SoC sim?
Date: Fri, 21 Oct 2011 22:36:48 +0200 [thread overview]
Message-ID: <4EA1D7E0.9070300@web.de> (raw)
In-Reply-To: <20111021072617.GA2130@cs.nctu.edu.tw>
Am 21.10.2011 09:26, schrieb 陳韋任:
> COREMU treats QEMU as an entity and lauches multiple QEMUs at the same
> time. QEMUs communicates to each other by using a underlying thin layer
> provided by COREMU.
> I think this approach is much clean than trying to
> parallelize QEMU itself.
In this case I disagree. Given shared global memory and peripherals in
the SoC case, any IPC or shared-memory setup is destined to create
performance or management overhead.
When there's independent nodes connected via CAN/LIN/FlexRay, then I
agree that multiple processes communicating via UNIX sockets make a lot
of sense.
My use case here is testing and debugging, so I think we could live with
the blocks being executed in an interleaved fashion until someone has
the ultimate parallelization solution for upstream.
Regards,
Andreas
next prev parent reply other threads:[~2011-10-21 20:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 18:44 [Qemu-devel] Multi heterogenous CPU archs for SoC sim? Greg McGary
2011-05-25 19:20 ` Peter Maydell
2011-05-26 19:11 ` Blue Swirl
2011-05-26 20:07 ` Lluís
2011-05-26 20:31 ` Blue Swirl
2011-05-27 14:23 ` Lluís
2011-10-20 22:51 ` Andreas Färber
2011-10-21 6:58 ` Peter Maydell
2011-10-21 7:26 ` 陳韋任
2011-10-21 20:36 ` Andreas [this message]
2011-10-22 8:12 ` 陳韋任
2011-10-21 15:41 ` Lluís Vilanova
2011-10-21 22:05 ` Andreas Färber
2011-10-22 9:32 ` Peter Maydell
2011-05-26 20:10 ` Andreas Färber
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=4EA1D7E0.9070300@web.de \
--to=andreas.faerber@web.de \
--cc=blauwirbel@gmail.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=greg.mcgary@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=xscript@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.