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,
scgl@linux.ibm.com
Subject: [kvm-unit-tests PATCH v4 0/1] s390x: add migration test for storage keys
Date: Wed, 8 Jun 2022 15:13:27 +0200 [thread overview]
Message-ID: <20220608131328.6519-1-nrb@linux.ibm.com> (raw)
v3->v4:
----
* remove useless goto (Thanks Thomas)
v2->v3:
----
* remove some useless variables, style suggestions, improve commit description
(thanks Janis)
* reverse christmas tree (thanks Claudio)
v1->v2:
----
* As per discussion with Janis and Claudio, remove the actual access check from
the test. This also allows us to remove the check_pgm_int_code_xfail() patch.
* Typos/Style suggestions (thanks Janis)
Upon migration, we expect storage keys set by the guest to be preserved,
so add a test for it.
We keep 128 pages and set predictable storage keys. Then, we migrate and check
they can be read back.
Nico Boehr (1):
s390x: add migration test for storage keys
s390x/Makefile | 1 +
s390x/migration-skey.c | 73 ++++++++++++++++++++++++++++++++++++++++++
s390x/unittests.cfg | 4 +++
3 files changed, 78 insertions(+)
create mode 100644 s390x/migration-skey.c
--
2.36.1
next reply other threads:[~2022-06-08 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 13:13 Nico Boehr [this message]
2022-06-08 13:13 ` [kvm-unit-tests PATCH v4 1/1] s390x: add migration test for storage keys Nico Boehr
2022-06-10 8:49 ` Janosch Frank
2022-06-10 11:56 ` Claudio Imbrenda
2022-06-13 9:19 ` [kvm-unit-tests PATCH v4 1/1] s390x: add migration test for storage keys:q! Nico Boehr
2022-06-08 13:39 ` [kvm-unit-tests PATCH v4 0/1] s390x: add migration test for storage keys 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=20220608131328.6519-1-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=scgl@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.