From: Peter Xu <peterx@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Fam Zheng" <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.12] monitor: bind dispatch bh to iohandler context
Date: Wed, 4 Apr 2018 08:39:17 +0800 [thread overview]
Message-ID: <20180404003917.GF26441@xz-mi> (raw)
In-Reply-To: <e9d37d29-82ae-ac3e-9919-62586206c88a@redhat.com>
On Tue, Apr 03, 2018 at 08:02:44AM -0500, Eric Blake wrote:
> On 04/03/2018 12:01 AM, Peter Xu wrote:
> > Eric Auger reported the problem days ago that OOB broke ARM when running
> > with libvirt:
> >
> > http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html
> >
> > This patch fixes the problem.
> >
> > It's not really needed now since we have turned OOB off now, but it's
> > still a bug fix, and it'll start to work when we turn OOB on for ARM.
>
> It may be more than just ARM affected, and just that ARM happened to
> trigger the problem easier.
Yes. Please feel free to add something to the commit message if you
think necessary.
[...]
> > This patch will fix all known OOB breakages I know so far, but I think
> > for better safety I'll still keep OOB off, and I'll send another patch
> > to turn default OOB on after 2.12 release.
>
> Yes, leaving OOB defaulting to off unless you use x-oob=on for 2.12 is
> the most conservative action, although we still want to fix all known
> bugs that you can trigger by using that.
>
> How did you run iotests with OOB on by default, by recompiling the
> binary to undo commit be933ffc2, or by tweaking the iotests scripts to
> pass x-oob=on by default?
Not really undo be933ffc2, but pick up 3fd2457d18 manually.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-04-04 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 5:01 [Qemu-devel] [PATCH for-2.12] monitor: bind dispatch bh to iohandler context Peter Xu
2018-04-03 7:02 ` Peter Xu
2018-04-03 8:40 ` Fam Zheng
2018-04-03 13:02 ` Eric Blake
2018-04-04 0:39 ` Peter Xu [this message]
2018-04-04 14:22 ` Stefan Hajnoczi
2018-04-04 15:07 ` Eric Blake
2018-04-05 12:34 ` Stefan Hajnoczi
2018-04-08 5:14 ` Peter Xu
2018-04-08 5:12 ` Peter Xu
2018-04-09 7:00 ` Stefan Hajnoczi
2018-04-10 3:08 ` Stefan Hajnoczi
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=20180404003917.GF26441@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).