From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>,
Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"John Williams" <john.williams@xilinx.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Building QEMU with multiple CPU targets.
Date: Mon, 08 Oct 2012 15:23:56 -0500 [thread overview]
Message-ID: <87obkc3e77.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA9Tt8nDXYLARM=M9YT4YYEF6Vh7Yym7bJb6z=3VLgZHeg@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 8 October 2012 07:39, Peter Crosthwaite
> <peter.crosthwaite@petalogix.com> wrote:
>> Im currently investigating the possibility of building QEMU with
>> multiple CPU architectures active concurrently. That is, I have a
>> binary with both an target-arm and target-microblaze and wish to run
>> them as a heterogeneous multiprocessor platform.
>>
>> Given the recent QOM development in making CPUs just another object,
>> shouldn't be possible with a bit of Makefile and configure rework to
>> build qemu-system-arm+microblaze and then create machine models
>> instantiating both CPU types?
>>
>> Are the major complications here from either a Make or QOM perspective?
>
> I certainly think this would be a nice feature to have, but I suspect
> the makefile/QOM bits are probably the easy parts :-)
>
> At the moment things like the translated code cache are basically
> globals and would need to be moved to be per-CPU. Also there are
> still various settings that are compile time which would need to
> become runtime (though we just got rid of the 'size of physical
> address type' one at least).
>
> -- PMM
It may be possible to cheat and compile the TCG + CPU code multiple
times as dynamic libraries. You can then load the libraries with
dlopen() with local symbol resolution.
Then it's mostly just a build file exercise.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-10-08 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 6:39 [Qemu-devel] Building QEMU with multiple CPU targets Peter Crosthwaite
2012-10-08 10:54 ` Peter Maydell
2012-10-08 11:17 ` Evgeny Voevodin
2012-10-08 20:23 ` Anthony Liguori [this message]
2012-10-08 20:31 ` Peter Maydell
2012-10-08 20:53 ` Anthony Liguori
2012-10-09 22:21 ` Edgar E. Iglesias
2012-10-19 6:54 ` Peter Crosthwaite
2012-10-08 13:17 ` Andreas Färber
2012-10-08 21:23 ` Stefan Weil
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=87obkc3e77.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=john.williams@xilinx.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.org \
--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).