qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
	qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Fam Zheng" <famz@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>,
	"Eric Auger" <eric.auger@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC] monitor: turn on Out-Of-Band by default again
Date: Wed, 30 May 2018 20:10:57 +0800	[thread overview]
Message-ID: <20180530121057.GE27442@xz-mi> (raw)
In-Reply-To: <20180530080458.GB27442@xz-mi>

On Wed, May 30, 2018 at 04:04:58PM +0800, Peter Xu wrote:
> On Tue, May 22, 2018 at 02:40:26PM -0400, John Snow wrote:
> > 
> > 
> > On 05/21/2018 10:13 AM, Eric Blake wrote:
> > > On 05/21/2018 03:42 AM, Peter Xu wrote:
> > >> We turned Out-Of-Band feature of monitors off for 2.12 release.  Now we
> > >> try to turn that on again.
> > > 
> > > "try to turn" sounds weak, like you aren't sure of this patch.  If you
> > > aren't sure, then why should we feel safe in applying it?  This text is
> > > going in the permanent git history, so sound bold, rather than hesitant!
> > > 
> > > "We have resolved the issues from last time (commit 3fd2457d reverted by
> > > commit a4f90923):
> > > - issue 1 ...
> > > - issue 2 ...
> > > So now we are ready to enable advertisement of the feature by default"
> > > 
> > > with better descriptions of the issues that you fixed (I can think of at
> > > least the fixes adding thread-safety to the current monitor, and fixing
> > > early use of the monitor before qmp_capabilities completes; there may
> > > also be other issues that you want to call out).
> > > 
> > >>
> > >> Signed-off-by: Peter Xu <peterx@redhat.com>
> > >> -- 
> > >> Now OOB should be okay with all known tests (except iotest qcow2, since
> > >> it is still broken on master),
> > > 
> > > Which tests are still failing for you?  Ideally, you can still
> > > demonstrate that the tests not failing without this patch continue to
> > > pass with this patch, even if you call out the tests that have known
> > > issues to still be resolved.
> > > 
> > 
> > Probably 91 and 169. If any others fail that's news to me.
> 
> I just gave it a shot on my workstation too (./check -qcow2):
> 
> Not run: 045 059 064 070 075 076 077 078 081 083 084 088 092 093 094 101 106 109 113 116 119 123 128 131 135 136 146 148 149 160 162 171 173 175 199 207 210 3
> Failures: 087 188 189 198 206
> Failed 5 of 167 tests
> 
> I'm testing against master, e609fa7.

Hmm... I ran again the same test and the same master commit but this
time it passed all 167 tests on my laptop.  So I assume the previous 5
failures are unreproducable at least every time (or there might be
something wrong with my testbed).  I'll rerun some more times, and
when I post the OOB patch I'll cover all correct qcow2 tests.

Regards,

-- 
Peter Xu

      reply	other threads:[~2018-05-30 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21  8:42 [Qemu-devel] [RFC] monitor: turn on Out-Of-Band by default again Peter Xu
2018-05-21  8:59 ` Daniel P. Berrangé
2018-05-21 10:41   ` Peter Xu
2018-05-21 14:13 ` Eric Blake
2018-05-22  3:39   ` Peter Xu
2018-05-24  7:08     ` Markus Armbruster
2018-05-24  7:34       ` Peter Xu
2018-05-29 19:00         ` Dr. David Alan Gilbert
2018-06-01 12:39       ` Stefan Hajnoczi
2018-05-22 18:40   ` John Snow
2018-05-30  8:04     ` Peter Xu
2018-05-30 12:10       ` Peter Xu [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=20180530121057.GE27442@xz-mi \
    --to=peterx@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=eblake@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=peter.maydell@linaro.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).