From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com
Subject: [kvm-unit-tests PATCH v2 0/4] s390x: Add skey removal facility test
Date: Wed, 28 Aug 2019 13:36:11 +0200 [thread overview]
Message-ID: <20190828113615.4769-1-frankja@linux.ibm.com> (raw)
The storage key removal facility (skrf) is an anti-facility, which
makes skey related instructions result in a special operation
exception when they handle storage keys. E.g. pfmf in clearing mode
does not result in an exception, but pfmf key setting does.
The skrf is always active in protected virtualization guests and can
be emulated by KVM (expected to be upstreamed with the remaining hpage
patches).
v2:
* Added march z12 bump patch
* Addressed review
Janosch Frank (4):
s390x: Move pfmf to lib and make address void
s390x: Storage key library functions now take void ptr addresses
s390x: Bump march to zEC12
s390x: Add storage key removal facility
lib/s390x/asm/mem.h | 40 +++++++++++---
s390x/Makefile | 3 +-
s390x/pfmf.c | 71 +++++++++---------------
s390x/skey.c | 29 +++++-----
s390x/skrf.c | 128 ++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 205 insertions(+), 66 deletions(-)
create mode 100644 s390x/skrf.c
--
2.17.0
next reply other threads:[~2019-08-28 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 11:36 Janosch Frank [this message]
2019-08-28 11:36 ` [kvm-unit-tests PATCH v2 1/4] s390x: Move pfmf to lib and make address void Janosch Frank
2019-08-28 11:39 ` Thomas Huth
2019-08-28 11:36 ` [kvm-unit-tests PATCH v2 2/4] s390x: Storage key library functions now take void ptr addresses Janosch Frank
2019-08-28 11:36 ` [kvm-unit-tests PATCH v2 3/4] s390x: Bump march to zEC12 Janosch Frank
2019-08-28 11:41 ` Thomas Huth
2019-08-28 11:36 ` [kvm-unit-tests PATCH v2 4/4] s390x: Add storage key removal facility Janosch Frank
2019-08-28 12:02 ` Thomas Huth
2019-08-28 14:05 ` Janosch Frank
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=20190828113615.4769-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.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