From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Peter Crosthwaite" <peter.crosthwaite@petalogix.com>,
"John Williams" <john.williams@xilinx.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] Building QEMU with multiple CPU targets.
Date: Mon, 08 Oct 2012 15:53:37 -0500 [thread overview]
Message-ID: <877gr0u1m6.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA8fBBECMQAO-qvJMwSJ1pHcNbMLTUW2dxj2uWkk0ArF5A@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 8 October 2012 21:23, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> 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.
>
> ...and when the common code wants to (say) call cpu_exit() on a
> particular core, how does it know which DLL's version to call?
> That said, I have a feeling I've heard about people trying this
> kind of approach before, so it's probably possible to get something
> that works on at least one host OS. I think doing it "properly"
> would be less of a hack, though...
I think you basically need to treat a "foreign" CPU separately from a
local CPU. You would load foreign CPUs as libraries and interact with
it separately.
I think the initial focus should be on hacking something to work. Then
we can figure out what's the best path to merging.
Regards,
Anthony Liguori
>
> -- PMM
next prev parent reply other threads:[~2012-10-08 20:53 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 [this message]
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=877gr0u1m6.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 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.