From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Beraldo Leal <bleal@redhat.com>,
qemu-block@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
Cleber Rosa <crosa@redhat.com>, John Snow <jsnow@redhat.com>
Subject: [PATCH v2 0/4] iotests: finalize switch to async QMP
Date: Mon, 21 Mar 2022 16:33:11 -0400 [thread overview]
Message-ID: <20220321203315.909411-1-jsnow@redhat.com> (raw)
GitLab: https://gitlab.com/jsnow/qemu/-/commits/python-qmp-legacy-switch-pt1b
CI: https://gitlab.com/jsnow/qemu/-/pipelines/495951187
This series isolates the iotests-centric changes required to switch to
the new QMP library. It doesn't do a whole lot!
This is a re-send just being sent for the purposes of aggregating tags
before pulling it into my Python branch.
John Snow (4):
python/machine: permanently switch to AQMP
scripts/bench-block-job: switch to AQMP
iotests/mirror-top-perms: switch to AQMP
iotests: switch to AQMP
python/qemu/machine/machine.py | 18 +++++++-----------
python/qemu/machine/qtest.py | 2 +-
scripts/simplebench/bench_block_job.py | 3 +--
tests/qemu-iotests/iotests.py | 3 +--
tests/qemu-iotests/tests/mirror-top-perms | 9 +++------
5 files changed, 13 insertions(+), 22 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-21 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 20:33 John Snow [this message]
2022-03-21 20:33 ` [PATCH v2 1/4] python/machine: permanently switch to AQMP John Snow
2022-03-21 20:33 ` [PATCH v2 2/4] scripts/bench-block-job: " John Snow
2022-03-21 20:33 ` [PATCH v2 3/4] iotests/mirror-top-perms: " John Snow
2022-03-21 20:33 ` [PATCH v2 4/4] iotests: " John Snow
2022-03-21 21:16 ` [PATCH v2 0/4] iotests: finalize switch to async QMP John Snow
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=20220321203315.909411-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=eduardo@habkost.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).