From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46120) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R5fYg-0001L0-7R for qemu-devel@nongnu.org; Mon, 19 Sep 2011 11:15:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R5fYe-00023c-SR for qemu-devel@nongnu.org; Mon, 19 Sep 2011 11:14:58 -0400 Received: from mail-yi0-f45.google.com ([209.85.218.45]:33852) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R5fYe-00023W-Q3 for qemu-devel@nongnu.org; Mon, 19 Sep 2011 11:14:56 -0400 Received: by yib2 with SMTP id 2so5146262yib.4 for ; Mon, 19 Sep 2011 08:14:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4E765171.8050108@mail.berlios.de> References: <4E74FC29.1050003@mail.berlios.de> <4E760AB2.50007@mail.berlios.de> <4E765171.8050108@mail.berlios.de> From: Mulyadi Santosa Date: Mon, 19 Sep 2011 22:14:15 +0700 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [PATCH 0/8] tcg/interpreter: Add TCG + interpreter for bytecode (virtual machine) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: QEMU Developers Hi Stefan.... On Mon, Sep 19, 2011 at 03:15, Stefan Weil wrote: > Am 18.09.2011 18:39, schrieb Mulyadi Santosa: >> On Sun, Sep 18, 2011 at 22:13, Stefan Weil wrote: >> So, that interpreter, should it be build inside Qemu too? Or can we >> use/write external one? let's say creating one in python and TCI >> passes the generated bytecode via UNIX socket to the listening Python >> script, is that doable or one of the goal your design? > > Do you think of something like http://bellard.org/jslinux/? None specific, but yes, that could be something that describe my idea :) (anyway, that jslinux is awesome so to speak). > The current interpreter is built inside QEMU, and I'm afraid > that separating code generator and interpreter in different > processes might be a lot of work. Maybe running both in > separate threads would be possible, so the code generator > could prepare new bytecode while the interpreter is still > running the previous one. Hm, got it...thanks for your kind explanation. I am very appreciate it. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com