qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	Jiri Denemark <jdenemar@redhat.com>,
	Eric Blake <eblake@redhat.com>, qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Move autoconverge out of experimental?
Date: Wed, 20 Apr 2016 09:25:38 +0530	[thread overview]
Message-ID: <20160420035538.GB4735@grmbl.mre> (raw)
In-Reply-To: <57163282.3040801@linux.vnet.ibm.com>

On (Tue) 19 Apr 2016 [09:28:34], Jason J. Herne wrote:
> On 04/19/2016 02:39 AM, Amit Shah wrote:
> >Hi Jason,
> >
> >We've had the new autoconverge features enabled for a full release
> >now, what are your thoughts on dropping the x- ?
> >
> >Some factors I consider are direct user feedback, changes to the
> >functionality / API, and higher-level user feedback (like libvirt).  I
> >believe libvirt is now using the new options, and they've not
> >complained.  So we could be ready to drop the x- prefix.
> >
> >Thoughts?
> >
> 
> Hi Amit,
> 
> Yes, I agree with you. We can probably drop the x-. The new autoconverge
> behavior was actually "in place" for the entire release. It was only the new
> commands to adjust throttling parameters that were marked as experimental.
> It is great that no one found any bugs. Let's hope it stays that way :)

OK - can you send a patch?  It'll be a 2.7 patch, though.

Our QE team also recently started testing the new autoconverge, so if
there's anything in there, it would be known soon :-)

Thanks,

		Amit

      reply	other threads:[~2016-04-20  3:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  6:39 [Qemu-devel] Move autoconverge out of experimental? Amit Shah
2016-04-19 13:28 ` Jason J. Herne
2016-04-20  3:55   ` Amit Shah [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=20160420035538.GB4735@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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;
as well as URLs for NNTP newsgroup(s).