From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "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>,
peterx@redhat.com, "Eric Auger" <eric.auger@redhat.com>,
"Eric Blake" <eblake@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/6] monitor: enable OOB by default
Date: Fri, 15 Jun 2018 09:42:43 +0800 [thread overview]
Message-ID: <20180615014249.22730-1-peterx@redhat.com> (raw)
Patches 1-3 are new. I am not sure about patch 3; I hope current hack
works for us.
v3:
- drop patch "tests: iotests: don't compare SHUTDOWN event", replace
it with "monitor: flush qmp responses when CLOSED" to fix up the
race. [Eric, Markus]
- tweak the oob revert patch to not break qmp-test [Eric]
- quite a few comment and commit message fix-ups [Eric]
- add more comment in commit message, mention about why MUX can't be
used for Out-Of-Band [Markus]
- one new patch to comment on chardev CLOSED event [Stefan]
- one new patch to fix iotest breakage on 060 specifically
Tests: make check, iotests
Please review. Thanks,
Peter Xu (6):
chardev: comment details for CLOSED event
monitor: flush qmp responses when CLOSED
tests: iotests: drop some stderr line
docs: mention shared state protect for OOB
monitor: remove "x-oob", turn oob on by default
Revert "tests: Add parameter to qtest_init_without_qmp_handshake"
docs/devel/qapi-code-gen.txt | 3 +++
include/chardev/char.h | 11 ++++++++-
include/monitor/monitor.h | 1 -
tests/libqtest.h | 4 +--
monitor.c | 47 ++++++++++++++++++++----------------
tests/libqtest.c | 10 +++-----
tests/qmp-test.c | 6 ++---
vl.c | 5 ----
tests/qemu-iotests/060 | 10 +++++++-
tests/qemu-iotests/060.out | 1 -
10 files changed, 56 insertions(+), 42 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-15 1:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 1:42 Peter Xu [this message]
2018-06-15 1:42 ` [Qemu-devel] [PATCH v3 1/6] chardev: comment details for CLOSED event Peter Xu
2018-06-15 12:49 ` Markus Armbruster
2018-06-18 15:55 ` Stefan Hajnoczi
2018-06-15 1:42 ` [Qemu-devel] [PATCH v3 2/6] monitor: flush qmp responses when CLOSED Peter Xu
2018-06-15 8:11 ` Markus Armbruster
2018-06-19 4:35 ` Peter Xu
2018-06-19 13:40 ` Markus Armbruster
2018-06-15 1:42 ` [Qemu-devel] [PATCH v3 3/6] tests: iotests: drop some stderr line Peter Xu
2018-06-15 8:13 ` Markus Armbruster
2018-06-19 4:41 ` Peter Xu
2018-06-15 1:42 ` [Qemu-devel] [PATCH v3 4/6] docs: mention shared state protect for OOB Peter Xu
2018-06-15 12:37 ` Markus Armbruster
2018-06-19 4:49 ` Peter Xu
2018-06-15 1:42 ` [Qemu-devel] [PATCH v3 5/6] monitor: remove "x-oob", turn oob on by default Peter Xu
2018-06-15 1:42 ` [Qemu-devel] [PATCH v3 6/6] Revert "tests: Add parameter to qtest_init_without_qmp_handshake" Peter Xu
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=20180615014249.22730-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@redhat.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).