From: Avi Kivity <avi@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org,
Uri Lublin <ulublin@redhat.com>
Subject: Re: [KVM-AUTOTEST PATCH] KVM test: refactor kvm_config.py
Date: Wed, 09 Feb 2011 12:19:23 +0200 [thread overview]
Message-ID: <4D526A2B.5050303@redhat.com> (raw)
In-Reply-To: <4D526755.8080903@redhat.com>
On 02/09/2011 12:07 PM, Michael Goldish wrote:
> On 02/09/2011 11:28 AM, Avi Kivity wrote:
> > On 02/09/2011 03:50 AM, Michael Goldish wrote:
> >> This is a reimplementation of the dict generator. It is much faster
> >> than the
> >> current implementation and uses a very small amount of memory.
> >> Running time
> >> and memory usage scale polynomially with the number of defined variants,
> >> compared to exponentially in the current implementation.
> >>
> >> Instead of regular expressions in the filters, the following syntax is
> >> used:
> >>
> >> , means OR
> >> .. means AND
> >> . means IMMEDIATELY-FOLLOWED-BY
> >>
> >> Example:
> >>
> >> only qcow2..Fedora.14, RHEL.6..raw..boot, smp2..qcow2..migrate..ide
> >>
> >
> >
> > Is it not possible to keep the old syntax? Breaking people's scripts is
> > bad.
>
> No, because the old syntax uses regexps and there's no clean way to
> prune tree branches early if those are supported.
>
Ok.
> For users who have their own tests_base.cfg (if there are any), we may
> have to keep the old parser as an alternative, or detect the presence of
> an incompatible cfg file and warn about it. Does that sound like a good
> idea?
No. It increases the maintenance burden and user confusion.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-09 10:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 1:50 [KVM-AUTOTEST PATCH] KVM test: refactor kvm_config.py Michael Goldish
2011-02-09 2:56 ` Cleber Rosa
2011-02-09 9:28 ` Avi Kivity
2011-02-09 10:07 ` Michael Goldish
2011-02-09 10:19 ` Avi Kivity [this message]
2011-02-10 1:18 ` Amos Kong
2011-02-10 12:42 ` Lucas Meneghel Rodrigues
2011-02-09 16:06 ` Ryan Harper
2011-02-09 16:21 ` Eduardo Habkost
2011-02-09 23:31 ` [Autotest] " Ryan Harper
2011-02-10 9:14 ` Michael Goldish
2011-02-10 10:34 ` [Autotest] " Avi Kivity
2011-02-10 10:46 ` Michael Goldish
2011-02-10 10:47 ` Avi Kivity
2011-02-10 10:55 ` Michael Goldish
2011-02-10 10:57 ` [Autotest] " Michael Goldish
2011-02-10 11:03 ` Avi Kivity
2011-02-10 11:46 ` Michael Goldish
2011-02-10 13:45 ` Eduardo Habkost
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=4D526A2B.5050303@redhat.com \
--to=avi@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mgoldish@redhat.com \
--cc=ulublin@redhat.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