From: Stefano Bonifazi <stefboombastic@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Raphaël Lefèvre" <taylor.lefevre@gmail.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: TCG flow vs dyngen
Date: Mon, 24 Jan 2011 14:20:13 +0100 [thread overview]
Message-ID: <4D3D7C8D.2070209@gmail.com> (raw)
In-Reply-To: <AANLkTinCKnw5RW=Rn3h2qy_z9iT+nWFCqLeg27GK=+OP@mail.gmail.com>
On 01/16/2011 08:24 PM, Peter Maydell wrote:
> 2011/1/16 Stefano Bonifazi<stefboombastic@gmail.com>:
>> I need to make the different instances of qemu-user exchange data ..
>> obviously keeping all of them in the same address space would be the easiest
>> way (unless I have to change all qemu code ;) )
>
> The problem is that you're trying to break a fundamental
> assumption made by a lot of qemu code. That's a large
> job which involves understanding, checking and possibly
> changing lots of already written code. In contrast, the
> code you need to exchange data between the instances is
> going to be fairly small and self contained and you'll already
> understand it because you've written it/will write it. I think
> it's pretty clear which one is going to be easier.
>
>>> Running each qemu as its own
>>> process and using interprocess communication for whatever
>>> coordination you need between the various instances seems
>>> more likely to be workable to me.
>
>> Exactly, it was the easiest way also for me.. and I've already done it,
>> works smoothly .. the only big problem is that it is not good for my
>> teacher.. he says it should work the dynamic library way o.O
>
> I think he's wrong. (You might like to think about what happens
> if the program being emulated in qemu user-mode does a fork()).
>
> Basically you're trying to do things the hard way; maybe
> you can get something that sort of works in the subset of
> cases you care about, but why on earth put in that much
> time and effort on something irrelevant to the actual problem
> you're trying to work on?
>
> -- PMM
>
>
Well my teacher's answer was that it is useless doing that, as there are
already plenty of solutions based on IPC .. they are interested in this
other approach, testing it .. They are not interested on how difficult
it can be for a student, how long it can take.. :(
Best regards,
Stefano B.
next prev parent reply other threads:[~2011-01-24 13:20 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 ` Stefano Bonifazi [this message]
2011-01-16 20:50 ` 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
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=4D3D7C8D.2070209@gmail.com \
--to=stefboombastic@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=taylor.lefevre@gmail.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 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).