public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Release plan for 0.12.0
Date: Mon, 5 Oct 2009 09:43:21 -0300	[thread overview]
Message-ID: <20091005094321.305e1876@doriath> (raw)
In-Reply-To: <4AC721C9.5030006@redhat.com>

On Sat, 03 Oct 2009 12:04:57 +0200
Avi Kivity <avi@redhat.com> wrote:

> On 10/01/2009 11:13 PM, Luiz Capitulino wrote:
> >> If we're going to support the protocol for 0.12, I'd like to most of the
> >> code merged by the end of October.
> >>      
> >   Four weeks.. Not so much time, but let's try.
> >
> >   There are two major issues that may delay QMP.
> >
> >   Firstly, we are still on the infrastructure/design phase, which
> > is natural to take time. Maybe when handlers start getting converted
> > en masse things will be faster.
> >    
> 
> I sure hope so.  Maybe someone can pitch in if not.

 I've written a TODO list if someone is willing to help:

http://tinyurl.com/ya7l6bo

> >   Secondly: testing. I have a very ugly python script to test the
> > already converted handlers. The problem is not only the ugliness,
> > the right way to do this would be to use kvm-autotest. So, I was
> > planning to take a detailed look at it and perhaps start writing
> > tests for QMP right when each handler is converted. Right Thing,
> > but takes time.
> >    
> 
> I think this could be done by having autotest use two monitors, one with 
> the machine protocol and one with the human protocol, trying first the 
> machine protocol and falling back if the command is not supported.

 Yes, sounds a good idea.

> Hopefully we can get the autotest people to work on it so we parallelize 
> development.  They'll also give user-oriented feedback which can be 
> valuable.

 I will talk to them about that.

> Are you using a standard json parser with your test script?  That's an 
> additional validation.

 I'm using Python's json module, but I could run one of the checkers
listed in the json's page for each test, before the Python's module
kicks in.

  reply	other threads:[~2009-10-05 12:44 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 23:54 Release plan for 0.12.0 Anthony Liguori
2009-09-30  0:20 ` Dustin Kirkland
2009-09-30  2:18   ` Anthony Liguori
2009-09-30  2:28 ` [Qemu-devel] " Isaku Yamahata
2009-09-30 13:03   ` Anthony Liguori
2009-09-30 13:43     ` Michael S. Tsirkin
2009-09-30  5:17 ` Amit Shah
2009-09-30 13:04   ` Anthony Liguori
2009-09-30 13:37     ` Amit Shah
2009-09-30 14:47       ` Anthony Liguori
2009-09-30 14:50         ` Amit Shah
2009-09-30  6:41 ` [Qemu-devel] " Avi Kivity
2009-09-30 13:05   ` Anthony Liguori
2009-10-01 21:13     ` Luiz Capitulino
2009-10-03 10:04       ` Avi Kivity
2009-10-05 12:43         ` Luiz Capitulino [this message]
2009-10-05 13:52           ` Avi Kivity
2009-09-30 13:31   ` Luiz Capitulino
2009-09-30  8:53 ` Michael Tokarev
2009-09-30  9:01   ` Avi Kivity
2009-09-30  9:31 ` Carl-Daniel Hailfinger
2009-09-30 13:07   ` Anthony Liguori
2009-09-30 15:59     ` Carl-Daniel Hailfinger
2009-09-30 19:25       ` Blue Swirl
2009-09-30 13:30 ` Luiz Capitulino
2009-09-30 14:45   ` Anthony Liguori
2009-09-30 15:03     ` Fred Leeflang
2009-09-30 15:26       ` [Qemu-devel] " Luiz Capitulino
2009-09-30 17:03     ` Juan Quintela
2009-09-30 19:28     ` [Qemu-devel] " Gerd Hoffmann
2009-10-03  4:28 ` TAKEDA, toshiya
2009-10-08 13:55 ` [Qemu-devel] " Jens Osterkamp
2009-10-08 14:21   ` Anthony Liguori
2009-10-14 13:09     ` [Qemu-devel] " Arnd Bergmann
2009-10-14 13:53       ` Anthony Liguori
2009-10-14 14:01         ` Michael S. Tsirkin
2009-10-14 14:04       ` Michael S. Tsirkin
2009-10-14 13:21     ` Michael S. Tsirkin
2009-10-14 14:17       ` Anthony Liguori
2009-10-14 14:24         ` Michael S. Tsirkin
2009-10-14 15:19           ` [Qemu-devel] " Jamie Lokier
2009-10-14 15:50             ` Michael S. Tsirkin
2009-10-14 21:10               ` [Qemu-devel] " Sridhar Samudrala
2009-10-14 22:53                 ` Raw vs. tap (was: Re: Re: Release plan for 0.12.0) Anthony Liguori
2009-10-15  6:36                   ` Raw vs. tap (was: Re: [Qemu-devel] " Mark McLoughlin
2009-10-15  7:56                   ` Raw vs. tap (was: " Michael S. Tsirkin
2009-10-15 13:32                     ` Raw vs. tap Anthony Liguori
2009-10-15 15:04                       ` Michael S. Tsirkin
2009-10-15 15:18                         ` Anthony Liguori
2009-10-15 15:48                           ` Michael S. Tsirkin
2009-10-15 18:37                             ` Anthony Liguori
2009-10-15 22:08                               ` Michael S. Tsirkin
2009-10-18 10:05                             ` Michael S. Tsirkin
2009-10-15  7:51                 ` [Qemu-devel] Re: Release plan for 0.12.0 Michael S. Tsirkin
2009-10-20  6:33 ` Takahiro Hirofuchi

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=20091005094321.305e1876@doriath \
    --to=lcapitulino@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /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