qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Crosthwaite <peter.crosthwaite@petalogix.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	John Williams <john.williams@xilinx.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] Building QEMU with multiple CPU targets.
Date: Mon, 08 Oct 2012 23:23:34 +0200	[thread overview]
Message-ID: <50734456.7030006@weilnetz.de> (raw)
In-Reply-To: <5072D26A.2040501@suse.de>

Am 08.10.2012 15:17, schrieb Andreas Färber:
> Hi Peter,
>
> Am 08.10.2012 08:39, schrieb Peter Crosthwaite:
>> 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.

If this works, it will also be possible to create a single
"qemu" executable for all system emulations.

>>
>> 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?
> Neither. The major complication is cpu.h and the per-target functions it
> defines/declares.
>
> My CPUState refactoring was a step into that direction, to get a solid
> QOM base class rather than macro contents inserted in the middle of the
> CPUArchState struct.

Adding an entry for the guest endianess to the CPU state
is also needed when the emulated system includes
CPUs with different endianess. Today we have conditional
compilation based on TARGET_WORDS_BIGENDIAN.

Regards

Stefan

      reply	other threads:[~2012-10-08 21:23 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
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 [this message]

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=50734456.7030006@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=afaerber@suse.de \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@xilinx.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@petalogix.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).