From: Stefano Bonifazi <stefboombastic@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: TCG flow vs dyngen
Date: Mon, 24 Jan 2011 15:00:43 +0100 [thread overview]
Message-ID: <4D3D860B.5050502@gmail.com> (raw)
In-Reply-To: <87zkqqv2yi.fsf@ginnungagap.bsc.es>
On 01/24/2011 02:36 PM, Lluís wrote:
> Stefano Bonifazi writes:
>
>> Do you mean what is my final goal?
> Exactly. A higher level perspective of what is our ultimate goal might
> help others figure out better ways to do it.
>
> Right now I don't remember what you posted your where technically trying
> to do, but I do remember it looked convoluted to me.
>
>
> Lluis
>
Sorry if I could not explain it better before, but it was not totally
clear for me too since the beginning, as I get new specs from my teacher
on the way, according what I manage to do, and where I find big obstacles!
Now, the final goal is to get multiple instances of qemu-ppc driven by a
systemc project executing on a x86 machine, with the different qemu-ppc
instances used as emulators for power-pc binaries.. I would get the
results of the run of the various ppc binaries back to the systemc
project and work with the results then.
I've already managed to integrate systemc with qemu-ppc, and I managed
to load multiple instances of qemu together, by loading it as a dynamic
library.
I think much confusion about my goals was originated by the fact that
the first attempt (failed) was to use qemu-user for loading many target
binaries one after the other.. Then I changed for having many instances
of qemu-user at the same time inside the same process..
The actual problem is letting qemu-user able of loading target code at a
different address than the one chosen by the link editor when creating
the binary..
If you are interested in that I've just created a new post about it:
http://lists.nongnu.org/archive/html/qemu-devel/2011-01/msg02361.html
Best regards,
Stefano B.
next prev parent reply other threads:[~2011-01-24 14:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 14:46 [Qemu-devel] TCG flow vs dyngen Raphael Lefevre
2011-01-16 15:21 ` Stefano Bonifazi
2011-01-16 16:01 ` Raphaël Lefèvre
2011-01-16 16:43 ` Stefano Bonifazi
2011-01-16 18:29 ` Peter Maydell
2011-01-16 19:02 ` Stefano Bonifazi
2011-01-16 19:24 ` Peter Maydell
2011-01-24 13:20 ` [Qemu-devel] " Stefano Bonifazi
2011-01-16 20:50 ` [Qemu-devel] " Stefano Bonifazi
2011-01-16 21:08 ` Raphaël Lefèvre
2011-01-24 12:35 ` [Qemu-devel] " Stefano Bonifazi
2011-01-17 11:59 ` [Qemu-devel] " Lluís
2011-01-24 12:31 ` [Qemu-devel] " Stefano Bonifazi
2011-01-24 13:36 ` Lluís
2011-01-24 14:00 ` Stefano Bonifazi [this message]
2011-01-24 15:06 ` Lluís
2011-01-24 17:23 ` Stefano Bonifazi
2011-01-24 18:12 ` Lluís
2011-01-16 19:16 ` [Qemu-devel] " Raphaël Lefèvre
2011-01-23 21:50 ` Rob Landley
2011-01-23 22:25 ` Stefano Bonifazi
2011-01-23 23:40 ` Rob Landley
2011-01-24 10:17 ` Stefano Bonifazi
2011-01-24 18:20 ` Rob Landley
2011-01-24 21:16 ` Stefano Bonifazi
2011-01-25 1:19 ` Rob Landley
2011-01-25 8:53 ` Stefano Bonifazi
2011-01-24 14:32 ` Peter Maydell
2011-01-24 14:56 ` Stefano Bonifazi
2011-01-24 15:15 ` Lluís
2011-01-24 18:02 ` Dushyant Bansal
2011-01-24 19:38 ` Stefano Bonifazi
2011-01-25 7:56 ` Dushyant Bansal
2011-01-25 9:04 ` Stefano Bonifazi
2011-01-25 9:05 ` Edgar E. Iglesias
2011-01-25 9:28 ` Stefano Bonifazi
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=4D3D860B.5050502@gmail.com \
--to=stefboombastic@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 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.