From: Greg McGary <greg.mcgary@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Multi heterogenous CPU archs for SoC sim?
Date: Wed, 25 May 2011 11:44:37 -0700 [thread overview]
Message-ID: <4DDD4E15.1080404@mcgary.org> (raw)
I would like to create a QEMU model of an SoC that has several CPU cores having different architectures. I'm guessing this can be done. Has anyone has thought much about this, and/or have advice? FYI, I am reasonably experienced with QEMU--I ported it to a new proprietary generic-RISC architecture last year and have it running in linux-user mode and in system mode running a newly-ported linux kernel.
G
next reply other threads:[~2011-05-25 18:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 18:44 Greg McGary [this message]
2011-05-25 19:20 ` [Qemu-devel] Multi heterogenous CPU archs for SoC sim? 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
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=4DDD4E15.1080404@mcgary.org \
--to=greg.mcgary@gmail.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).