qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call minutes for Oct 19
Date: Wed, 20 Oct 2010 12:47:54 +0200	[thread overview]
Message-ID: <4CBEC8DA.1010403@redhat.com> (raw)
In-Reply-To: <4DE00079-05FA-40DF-9EA5-9573AD745117@suse.de>

  On 10/20/2010 10:21 AM, Alexander Graf wrote:
> On 19.10.2010, at 17:14, Chris Wright wrote:
>
> >  0.13.X -stable
> >  - Anthony will send note to qemu-devel on this
> >  - move 0.13.X -stable to a separate tree
> >  - driven independently of main qemu tree
> >  - challenge is always in the porting and testing of backported fixes
> >  - looking for volunteers
> >
> >  0.14
> >  - would like to do this before end of the year
> >  - 0.13 forked off a while back (~July),
> >  - 0.14 features
> >   - QMP stabilized
> >     - 0.13.0 ->  0.14 QMP
> >     - hard attempt not to break compatibility
> >     - new commands, rework, async, human monitor passthrough
> >     - goal getting to libvirt not needing human monitor at all
> >     - QMP KVM autotest test suite submitted
> >  - in-kernel apic, tpr patching still outstanding
> >  - QED coroutine concurrency
>
> Would it be realistic to declare deprecating the qemu-kvm fork for 0.14 as goal?

For general use perhaps, device assignment might need another cycle.

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2010-10-20 10:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 15:14 [Qemu-devel] KVM call minutes for Oct 19 Chris Wright
2010-10-20  8:21 ` Alexander Graf
2010-10-20  8:25   ` Paolo Bonzini
2010-10-20  8:30     ` Alexander Graf
2010-10-20 10:47   ` Avi Kivity [this message]
2010-10-20 12:16   ` Dor Laor
2010-10-21 10:22     ` Andrew Beekhof
2010-10-21 10:26       ` Dor Laor
2010-10-21 13:09       ` Anthony Liguori
2010-10-21 13:18         ` Daniel P. Berrange
2010-10-21 13:32           ` Anthony Liguori
2010-10-21 15:43             ` Andrew Beekhof
2010-10-21 16:25               ` Anthony Liguori
2010-10-21 16:37                 ` Chris Wright
2010-10-21 19:47                 ` Andrew Beekhof
2010-10-20 13:02   ` Anthony Liguori
2010-10-20 13:19     ` Daniel P. Berrange
2010-10-20 13:21       ` Anthony Liguori
2010-10-20 22:46         ` Dor Laor
2010-10-21  1:14           ` Alexander Graf
2010-10-21  7:45             ` Paolo Bonzini
2010-10-21 13:02               ` Anthony Liguori
2010-10-21 13:05                 ` Dor Laor
2010-10-22 17:29                 ` Chris Wright
2010-10-22 17:39                   ` Anthony Liguori
2010-10-22 18:20                     ` Chris Wright
2010-10-22 18:53                       ` Anthony Liguori
2010-10-23  0:06                         ` Chris Wright

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=4CBEC8DA.1010403@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).