From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:35178)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1Qz2KU-0008Bf-HS
	for qemu-devel@nongnu.org; Thu, 01 Sep 2011 04:08:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1Qz2KT-0007yS-HN
	for qemu-devel@nongnu.org; Thu, 01 Sep 2011 04:08:54 -0400
Received: from mail-ww0-f53.google.com ([74.125.82.53]:54974)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1Qz2KT-0007y5-CY
	for qemu-devel@nongnu.org; Thu, 01 Sep 2011 04:08:53 -0400
Received: by wwf25 with SMTP id 25so1531576wwf.10
	for <qemu-devel@nongnu.org>; Thu, 01 Sep 2011 01:08:52 -0700 (PDT)
Date: Thu, 1 Sep 2011 09:08:46 +0100
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20110901080846.GA14245@stefanha-thinkpad.localdomain>
References: <4E5EEBDE.2020806@mips.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E5EEBDE.2020806@mips.com>
Subject: Re: [Qemu-devel] python scripts
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: reed kotler <rkotler@mips.com>
Cc: "r >> \"Fuhler, Rich\"" <rich@mips.com>, qemu-devel@nongnu.org, "Johnson,
	Eric" <ericj@mips.com>

On Wed, Aug 31, 2011 at 07:20:14PM -0700, reed kotler wrote:
> I recently made a major addition (about 150 new instructions) to
> MIPS QEMU to add the DSP instructions for Mips  and Micro MIPS
> processors.
> 
> To make this process simpler and less error prone, I generated a
> large amount of the code and framework from python scripts. This
> code is much easier to produce and maintain.
> 
> I.e. python scripts producing C code and header files.
> 
> I would like to check the python scripts along with the changes to
> autoconf into QEMU and have the build process produce the C code.
> 
> We have another large project where we want to use this same
> technique again.
> 
> Is there any big objection to this?
> 
> The python is very simple and would probably work with python version 0.1.
> Of course the configure script can test for a proper python being present.

Python is already used to generate code for the QEMU Guest Agent
(qemu-ga) which is merged in qemu.git.  If you already have Python
patches ready, I suggest just sending them and seeing what people think.

Stefan