From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v1 2/2] s390x: add migration TOD clock test
Date: Fri, 26 Aug 2022 10:49:44 +0200 [thread overview]
Message-ID: <20220826084944.19466-3-nrb@linux.ibm.com> (raw)
In-Reply-To: <20220826084944.19466-1-nrb@linux.ibm.com>
On migration, we expect the guest clock value to be preserved. Add a
test to verify this:
- advance the guest TOD by much more than we need to migrate
- migrate the guest
- get the guest TOD
After migration, assert the guest TOD value is at least the value we set
before migration.
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
---
s390x/Makefile | 1 +
s390x/migration-sck.c | 45 +++++++++++++++++++++++++++++++++++++++++++
s390x/unittests.cfg | 4 ++++
3 files changed, 50 insertions(+)
create mode 100644 s390x/migration-sck.c
diff --git a/s390x/Makefile b/s390x/Makefile
index efd5e0c13102..be8e647bb35f 100644
--- a/s390x/Makefile
+++ b/s390x/Makefile
@@ -34,6 +34,7 @@ tests += $(TEST_DIR)/migration.elf
tests += $(TEST_DIR)/pv-attest.elf
tests += $(TEST_DIR)/migration-cmm.elf
tests += $(TEST_DIR)/migration-skey.elf
+tests += $(TEST_DIR)/migration-sck.elf
pv-tests += $(TEST_DIR)/pv-diags.elf
diff --git a/s390x/migration-sck.c b/s390x/migration-sck.c
new file mode 100644
index 000000000000..701d33f9db5a
--- /dev/null
+++ b/s390x/migration-sck.c
@@ -0,0 +1,45 @@
+/* SPDX-License-Identifier: GPL-2.0-only */
+/*
+ * SET CLOCK migration tests
+ *
+ * Copyright IBM Corp. 2022
+ *
+ * Authors:
+ * Nico Boehr <nrb@linux.ibm.com>
+ */
+
+#include <libcflat.h>
+#include <asm/time.h>
+#include <bitops.h>
+
+static void test_sck_migration(void)
+{
+ uint64_t now_before_set = 0, now_after_migration, time_to_set, time_to_advance;
+ int cc;
+
+ stckf(&now_before_set);
+
+ /* Advance the clock by a lot more than we might ever need to migrate (60s) */
+ time_to_advance = (60ULL * 1000ULL * 1000ULL << STCK_SHIFT_US);
+ time_to_set = now_before_set + time_to_advance;
+
+ cc = sck(&time_to_set);
+ report(!cc, "setting clock succeeded");
+
+ puts("Please migrate me, then press return\n");
+ (void)getchar();
+
+ cc = stckf(&now_after_migration);
+ report(!cc, "clock still set");
+
+ report(now_after_migration >= time_to_set, "TOD clock value preserved");
+}
+
+int main(void)
+{
+ report_prefix_push("migration-sck");
+
+ test_sck_migration();
+ report_prefix_pop();
+ return report_summary();
+}
diff --git a/s390x/unittests.cfg b/s390x/unittests.cfg
index f7b1fc3dbca1..808e8a28ba96 100644
--- a/s390x/unittests.cfg
+++ b/s390x/unittests.cfg
@@ -185,3 +185,7 @@ groups = migration
[migration-skey]
file = migration-skey.elf
groups = migration
+
+[migration-sck]
+file = migration-sck.elf
+groups = migration
--
2.36.1
next prev parent reply other threads:[~2022-08-26 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 8:49 [kvm-unit-tests PATCH v1 0/2] s390x: Add migration test for guest TOD clock Nico Boehr
2022-08-26 8:49 ` [kvm-unit-tests PATCH v1 1/2] lib/s390x: move TOD clock related functions to library Nico Boehr
2022-10-06 10:50 ` Claudio Imbrenda
2022-10-11 11:44 ` Nico Boehr
2022-08-26 8:49 ` Nico Boehr [this message]
2022-10-06 10:58 ` [kvm-unit-tests PATCH v1 2/2] s390x: add migration TOD clock test 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=20220826084944.19466-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=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