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 v1 0/2] s390x: add migration test for storage keys
Date: Thu, 12 May 2022 16:01:05 +0200 [thread overview]
Message-ID: <20220512140107.1432019-1-nrb@linux.ibm.com> (raw)
Upon migration, we expect storage keys being 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 and the respective access restrictions are in place when
the access key in the PSW doesn't match.
TCG currently doesn't implement key-controlled protection, hence add the
relevant tests as xfails. To this end, a check_pgm_int_xfail() is useful, which
is also added in this series.
Nico Boehr (2):
lib: s390x: introduce check_pgm_int_code_xfail()
s390x: add migration test for storage keys
lib/s390x/asm/interrupt.h | 1 +
lib/s390x/interrupt.c | 9 +++-
s390x/Makefile | 1 +
s390x/migration-skey.c | 98 +++++++++++++++++++++++++++++++++++++++
s390x/unittests.cfg | 4 ++
5 files changed, 111 insertions(+), 2 deletions(-)
create mode 100644 s390x/migration-skey.c
--
2.31.1
next reply other threads:[~2022-05-12 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 14:01 Nico Boehr [this message]
2022-05-12 14:01 ` [kvm-unit-tests PATCH v1 1/2] lib: s390x: introduce check_pgm_int_code_xfail() Nico Boehr
2022-05-12 15:23 ` Claudio Imbrenda
2022-05-12 14:01 ` [kvm-unit-tests PATCH v1 2/2] s390x: add migration test for storage keys Nico Boehr
2022-05-12 14:43 ` Janosch Frank
2022-05-12 15:41 ` Claudio Imbrenda
2022-05-13 12:15 ` Nico Boehr
2022-05-13 11:04 ` Janis Schoetterl-Glausch
2022-05-13 12:33 ` Claudio Imbrenda
2022-05-13 12:46 ` Janis Schoetterl-Glausch
2022-05-13 13:04 ` Claudio Imbrenda
2022-05-16 8:45 ` Nico Boehr
2022-05-13 13:02 ` Nico Boehr
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=20220512140107.1432019-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox