From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@kernel.org>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] s390: Reintroduce support for DCACHE_WORD_ACCESS
Date: Fri, 17 Jul 2026 11:05:12 +0200 [thread overview]
Message-ID: <1e04d9c8-ea80-4b19-8f56-9d622261964a@linux.ibm.com> (raw)
In-Reply-To: <20260716141436.2125703-1-hca@linux.ibm.com>
Am 16.07.26 um 16:14 schrieb Heiko Carstens:
> Support for DCACHE_WORD_ACCESS was recently removed [1] since it caused
> problems with the incomplete handling of secure storage access
> exceptions. It looked like fixing the exception handler would be a larger
> effort; therefore support for DCACHE_WORD_ACCESS was removed as a work
> around.
>
> Address the potential problems that exist with secure storage access
> exceptions and add support for DCACHE_WORD_ACCESS again.
>
> In particular address the following problems:
>
> - Reading the guest variable storage area via the /proc/kcore interface
> results in short reads. Address this by using a VM_SPARSE area for the
> guest variable storage area. VM_SPARSE areas will be handled like
> memory holes (zeros will be read).
>
> - Fix handling of secure storage access exceptions in vmalloc area.
>
> - Remove folio handling for secure storage access exceptions to avoid
> potential data corruption.
>
> [1] 37540b8c287f ("s390: Revert support for DCACHE_WORD_ACCESS")
>
> Heiko Carstens (4):
> KVM: s390: pv: Use VM_SPARSE area for guest variable storage area
> s390/mm: Fix handling of secure storage access exceptions in vmalloc area
> s390/mm: Remove folio handling for secure storage access exceptions
> s390: Add support for DCACHE_WORD_ACCESS (again)
Whole series
Tested-by: Christian Borntraeger <borntraeger@linux.ibm.com>
with a kernel module and a hacked up kselftest.
>
> arch/s390/Kconfig | 1 +
> arch/s390/include/asm/asm-extable.h | 4 ++
> arch/s390/include/asm/uv.h | 2 +
> arch/s390/include/asm/word-at-a-time.h | 22 ++++++++++
> arch/s390/kernel/uv.c | 59 ++++++++++++++++++++++++++
> arch/s390/kvm/pv.c | 6 +--
> arch/s390/mm/extable.c | 18 ++++++++
> arch/s390/mm/fault.c | 10 ++---
> 8 files changed, 112 insertions(+), 10 deletions(-)
>
prev parent reply other threads:[~2026-07-17 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 14:14 Heiko Carstens
2026-07-16 14:14 ` [PATCH 1/4] KVM: s390: pv: Use VM_SPARSE area for guest variable storage area Heiko Carstens
2026-07-16 14:14 ` [PATCH 2/4] s390/mm: Fix handling of secure storage access exceptions in vmalloc area Heiko Carstens
2026-07-16 14:14 ` [PATCH 3/4] s390/mm: Remove folio handling for secure storage access exceptions Heiko Carstens
2026-07-16 14:19 ` David Hildenbrand (Arm)
2026-07-16 14:14 ` [PATCH 4/4] s390: Add support for DCACHE_WORD_ACCESS (again) Heiko Carstens
2026-07-17 9:05 ` Christian Borntraeger [this message]
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=1e04d9c8-ea80-4b19-8f56-9d622261964a@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@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