From: reed kotler <rkotler@mips.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "r >> \"Fuhler, Rich\"" <rich@mips.com>,
qemu-devel@nongnu.org, "Johnson, Eric" <ericj@mips.com>
Subject: Re: [Qemu-devel] python scripts
Date: Thu, 1 Sep 2011 09:25:40 -0700 [thread overview]
Message-ID: <4E5FB204.3020802@mips.com> (raw)
In-Reply-To: <20110901080846.GA14245@stefanha-thinkpad.localdomain>
On 09/01/2011 01:08 AM, Stefan Hajnoczi wrote:
> 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
Awesome.
We are syncing to main branch and I will do some clean up this weekend
and hopefully we can have something you can look at on Tuesday.
We have a huge suite of MIPS internal tests for testing MIPS DSP
instructions and all these new instructions that we added pass. These
tests are the same ones used to certify real hardware.
Reed
prev parent reply other threads:[~2011-09-01 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 2:20 [Qemu-devel] python scripts reed kotler
2011-09-01 8:08 ` Stefan Hajnoczi
2011-09-01 16:25 ` reed kotler [this message]
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=4E5FB204.3020802@mips.com \
--to=rkotler@mips.com \
--cc=ericj@mips.com \
--cc=qemu-devel@nongnu.org \
--cc=rich@mips.com \
--cc=stefanha@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).