From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCH] signrom: Speed up checksum calculation
Date: Mon, 23 Jan 2012 14:08:02 -0600 [thread overview]
Message-ID: <4F1DBE22.609@codemonkey.ws> (raw)
In-Reply-To: <4F1DB432.3060804@mail.berlios.de>
On 01/23/2012 01:25 PM, Stefan Weil wrote:
> Am 23.01.2012 20:19, schrieb Jan Kiszka:
>> On 2012-01-23 20:16, Stefan Weil wrote:
>>> Am 23.01.2012 19:38, schrieb Jan Kiszka:
>>>
> [snip]
>>> What about replacing the whole script by a python script?
>>> That would save about 6 more forks :-)
>>
>> I think we have no python dependency in the build system yet - while we
>> have for awk. That was also the original reason to go for a shell script.
>>
>> If the situation changed, I would not vote against python, for sure.
>>
>> Jan
>
> We do. Even configure will fail now without Python:
>
> if ! has $python; then
> echo "Python not found. Use --python=/path/to/python"
> exit 1
> fi
>
> QEMU depends on Python = Python 2 for QAPI, tracing and maybe more.
> See scripts/*.py.
I've been thinking that we could potentially rewrite a large chunk (all?) of
configure in python too since we have such a hard dependency now.
Regards,
Anthony Liguori
>
> Stefan
>
>
next prev parent reply other threads:[~2012-01-23 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 18:38 [Qemu-devel] [RFC][PATCH] signrom: Speed up checksum calculation Jan Kiszka
2012-01-23 19:16 ` Stefan Weil
2012-01-23 19:19 ` Jan Kiszka
2012-01-23 19:25 ` Stefan Weil
2012-01-23 20:08 ` Anthony Liguori [this message]
2012-01-23 20:32 ` Jan Kiszka
2012-01-23 20:37 ` Anthony Liguori
2012-01-23 21:32 ` Stefan Weil
2012-01-24 9:43 ` Andreas Färber
2012-01-24 8:18 ` Paolo Bonzini
2012-01-24 10:18 ` Christoph Egger
2012-01-24 8:39 ` Paolo Bonzini
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=4F1DBE22.609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).