From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, david@kernel.org, nrb@linux.ibm.com,
schlameuss@linux.ibm.com, gra@linux.ibm.com
Subject: [PATCH v1 00/10] KVM: s390: Misc bugfixes and improvements for 7.4
Date: Thu, 22 Oct 2026 17:55:21 +0200 [thread overview]
Message-ID: <20261022155531.204593-1-imbrenda@linux.ibm.com> (raw)
Misc bugfixes and improvements.
Some are preparations for future patches, some are preventive fixes for
mostly theoretical issues, some are quality of life improvement (mostly
for the maintainers).
Claudio Imbrenda (10):
KVM: s390: Move some skey functions to headers
KVM: s390: Refactor and improve DAT tables handling
KVM: s390: Move prefix marker from PGSTEs to PTEs
KVM: s390: Automatically enable storage keys for UCONTROL VMs
KVM: s390: Replace ASCE usage with a struct with more flags
KVM: s390: Rework some helper functions
KVM: s390: Fix UCONTROL inconsistencies
KVM: s390: Improve unmapping of large ranges
KVM: s390: vsie: Fix pinning using the wrong flag
KVM: s390: Enable 1M pages by default
arch/s390/kvm/gmap/dat.c | 195 +++++++++++-------------
arch/s390/kvm/gmap/dat.h | 196 +++++++++++++++++-------
arch/s390/kvm/gmap/gmap.c | 281 +++++++++++++++++++++++------------
arch/s390/kvm/gmap/gmap.h | 38 +++--
arch/s390/kvm/gmap/kvm_mmu.c | 6 +-
arch/s390/kvm/s390/gaccess.c | 27 ++--
arch/s390/kvm/s390/priv.c | 15 +-
arch/s390/kvm/s390/pv.c | 11 +-
arch/s390/kvm/s390/s390.c | 46 +++---
arch/s390/kvm/s390/s390.h | 6 +-
arch/s390/kvm/s390/vsie.c | 135 +++++++----------
11 files changed, 539 insertions(+), 417 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-22 15:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:55 Claudio Imbrenda [this message]
2026-10-22 15:55 ` [PATCH v1 01/10] KVM: s390: Move some skey functions to headers Claudio Imbrenda
2026-10-22 15:58 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 02/10] KVM: s390: Refactor and improve DAT tables handling Claudio Imbrenda
2026-10-22 16:05 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 03/10] KVM: s390: Move prefix marker from PGSTEs to PTEs Claudio Imbrenda
2026-10-22 16:06 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 04/10] KVM: s390: Automatically enable storage keys for UCONTROL VMs Claudio Imbrenda
2026-10-22 16:13 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 05/10] KVM: s390: Replace ASCE usage with a struct with more flags Claudio Imbrenda
2026-10-22 16:09 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 06/10] KVM: s390: Rework some helper functions Claudio Imbrenda
2026-10-22 16:00 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 07/10] KVM: s390: Fix UCONTROL inconsistencies Claudio Imbrenda
2026-10-22 17:00 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 08/10] KVM: s390: Improve unmapping of large ranges Claudio Imbrenda
2026-10-22 16:53 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 09/10] KVM: s390: vsie: Fix pinning using the wrong flag Claudio Imbrenda
2026-10-22 16:02 ` sashiko-bot
2026-10-22 15:55 ` [PATCH v1 10/10] KVM: s390: Enable 1M pages by default Claudio Imbrenda
2026-10-22 16:11 ` sashiko-bot
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=20261022155531.204593-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=schlameuss@linux.ibm.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