From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Pinto <c.pinto@virtualopensystems.com>, qemu-devel@nongnu.org
Cc: Jani Kokkonen <Jani.Kokkonen@huawei.com>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
Claudio Fontana <Claudio.Fontana@huawei.com>
Subject: Re: [Qemu-devel] [RFC] Towards an Heterogeneous QEMU
Date: Fri, 31 Jul 2015 15:10:56 +0200 [thread overview]
Message-ID: <55BB73E0.6030408@redhat.com> (raw)
In-Reply-To: <55B63805.8050603@virtualopensystems.com>
On 27/07/2015 15:54, Christian Pinto wrote:
> From the user point of view there is usually an operating system
> booting on the Master processor (e.g. Linux) at platform startup,
> while the other processors are used to offload the Master one from
> some computation or to deal with real-time interfaces. It is the
> Master OS that triggers the boot of the Slave processors, and
> provides them also the binary code to execute (e.g. RTOS, binary
> firmware) by placing it into a pre-defined memory area that is
> accessible to the Slaves. Usually the memory for the Slaves is
> carved out from the Master OS during boot. Once a Slave is booted the
> two processors can communicate through queues in shared memory and
> inter-processor interrupts (IPIs). In Linux, it is the
> remoteproc/rpmsg framework that enables the control (boot/shutdown)
> of Slave processors, and also to establish a communication channel
> based on virtio queues.
>
> Currently, QEMU is not able to model such an architecture, mainly
> because only a single processor can be emulated at one time, and the
> OS binary image needs to be placed in memory at model startup.
Hi, you may be interested in the "multi-arch" patches here:
http://thread.gmane.org/gmane.comp.emulators.qemu/351808
These do roughly what you are saying, though in a single QEMU process.
Paolo
next prev parent reply other threads:[~2015-07-31 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 13:54 [Qemu-devel] [RFC] Towards an Heterogeneous QEMU Christian Pinto
2015-07-31 12:03 ` Christopher Covington
2015-07-31 16:23 ` Christian Pinto
2015-07-31 13:10 ` Paolo Bonzini [this message]
2015-07-31 16:47 ` Christian Pinto
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=55BB73E0.6030408@redhat.com \
--to=pbonzini@redhat.com \
--cc=Claudio.Fontana@huawei.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=c.pinto@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
/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.