From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, hreitz@redhat.com, dave@treblig.org,
thuth@redhat.com, qemu-block@nongnu.org, berrange@redhat.com,
dgilbert@redhat.com, qemu-trivial@nongnu.org
Subject: [PATCH 0/2] docs tests: Fix use of migrate_set_parameter
Date: Fri, 25 Aug 2023 17:59:21 +0200 [thread overview]
Message-ID: <20230825155923.1983141-1-armbru@redhat.com> (raw)
I spotted a bad use of migrate_set_parameter in test-hmp.c, and looked
for more.
I also looked for more failing HMP commands in test-hmp.c. I found
some, but they fail only on some machines, which feels okay. They
are:
* device_add usb-mouse,id=mouse1
device_del mouse1
Fail when the device is not compiled in, and when the machine
doesn't provide USB.
* memsave 0 4096 "/dev/null"
Fails when the machine doesn't have memory there.
* screendump /dev/null
Fails when there is no console.
* dump-guest-memory /dev/null 0 4096
Fails for targets that don't support dumping, and when the machine
doesn't have memory there.
* nmi
Fails when the machine doesn't provide NMIs.
Markus Armbruster (2):
docs tests: Fix use of migrate_set_parameter
tests/qtest/test-hmp: Fix migrate_set_parameter xbzrle-cache-size test
docs/multi-thread-compression.txt | 12 ++++++------
docs/rdma.txt | 2 +-
tests/qtest/test-hmp.c | 6 +++---
tests/qemu-iotests/181 | 2 +-
4 files changed, 11 insertions(+), 11 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-25 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 15:59 Markus Armbruster [this message]
2023-08-25 15:59 ` [PATCH 1/2] docs tests: Fix use of migrate_set_parameter Markus Armbruster
2023-08-25 16:13 ` Thomas Huth
2023-08-25 15:59 ` [PATCH 2/2] tests/qtest/test-hmp: Fix migrate_set_parameter xbzrle-cache-size test Markus Armbruster
2023-08-25 16:09 ` Thomas Huth
2023-08-29 17:37 ` [PATCH 0/2] docs tests: Fix use of migrate_set_parameter Michael Tokarev
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=20230825155923.1983141-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dave@treblig.org \
--cc=dgilbert@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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).