From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v3 2/4] s390x: add support for migration tests
Date: Wed, 20 Apr 2022 15:45:55 +0200 [thread overview]
Message-ID: <20220420134557.1307305-3-nrb@linux.ibm.com> (raw)
In-Reply-To: <20220420134557.1307305-1-nrb@linux.ibm.com>
Now that we have SCLP console read support, run our tests with migration_cmd, so
we can get migration support on s390x.
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
---
s390x/run | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/s390x/run b/s390x/run
index 064ecd1b337a..2bcdabbaa14f 100755
--- a/s390x/run
+++ b/s390x/run
@@ -25,7 +25,7 @@ M+=",accel=$ACCEL"
command="$qemu -nodefaults -nographic $M"
command+=" -chardev stdio,id=con0 -device sclpconsole,chardev=con0"
command+=" -kernel"
-command="$(timeout_cmd) $command"
+command="$(migration_cmd) $(timeout_cmd) $command"
# We return the exit code via stdout, not via the QEMU return code
run_qemu_status $command "$@"
--
2.31.1
next prev parent reply other threads:[~2022-04-20 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 13:45 [kvm-unit-tests PATCH v3 0/4] s390x: add migration test support Nico Boehr
2022-04-20 13:45 ` [kvm-unit-tests PATCH v3 1/4] lib: s390x: add support for SCLP console read Nico Boehr
2022-04-20 14:16 ` Claudio Imbrenda
2022-04-21 14:29 ` Janosch Frank
2022-04-22 7:50 ` Nico Boehr
2022-04-22 8:01 ` Janosch Frank
2022-04-20 13:45 ` Nico Boehr [this message]
2022-04-20 13:45 ` [kvm-unit-tests PATCH v3 3/4] s390x: don't run migration tests under PV Nico Boehr
2022-04-20 13:45 ` [kvm-unit-tests PATCH v3 4/4] s390x: add basic migration test Nico Boehr
2022-04-20 14:22 ` Claudio Imbrenda
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=20220420134557.1307305-3-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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