From: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
To: qemu-s390x@nongnu.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>
Cc: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
David Hildenbrand <david@redhat.com>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org
Subject: [PATCH 0/2] s390x: kvm: Honor storage keys during emulation
Date: Fri, 6 May 2022 17:39:54 +0200 [thread overview]
Message-ID: <20220506153956.2217601-1-scgl@linux.ibm.com> (raw)
Make use of the storage key support of the MEMOP ioctl, if available,
in order to support storage key checking during emulation.
I did not update all the headers, since that broke the build,
not sure what the best way of dealing with that is.
Janis Schoetterl-Glausch (2):
Pull in MEMOP changes in linux-headers
target/s390x: kvm: Honor storage keys during emulation
linux-headers/linux/kvm.h | 11 +++++++++--
target/s390x/kvm/kvm.c | 9 +++++++++
2 files changed, 18 insertions(+), 2 deletions(-)
base-commit: 31abf61c4929a91275fe32f1fafe6e6b3e840b2a
--
2.32.0
next reply other threads:[~2022-05-06 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:39 Janis Schoetterl-Glausch [this message]
2022-05-06 15:39 ` [PATCH 1/2] Pull in MEMOP changes in linux-headers Janis Schoetterl-Glausch
2022-05-06 15:39 ` [PATCH 2/2] target/s390x: kvm: Honor storage keys during emulation Janis Schoetterl-Glausch
2022-05-19 10:05 ` Thomas Huth
2022-05-19 13:53 ` Janis Schoetterl-Glausch
2022-05-24 10:43 ` Thomas Huth
2022-05-24 11:10 ` Christian Borntraeger
2022-05-24 11:21 ` Thomas Huth
2022-05-24 11:52 ` Janis Schoetterl-Glausch
2022-05-25 9:00 ` Thomas Huth
2022-05-24 16:08 ` Halil Pasic
2022-05-09 8:06 ` [PATCH 0/2] s390x: " Cornelia Huck
2022-05-10 13:32 ` Janis Schoetterl-Glausch
2022-05-10 13:43 ` Cornelia Huck
2022-05-12 8:52 ` Thomas Huth
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=20220506153956.2217601-1-scgl@linux.ibm.com \
--to=scgl@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).