From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Kevin Brodsky <kevin.brodsky@arm.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] s390/mm: Make PTC and UV call order consistent
Date: Thu, 23 Apr 2026 12:54:09 +0200 [thread overview]
Message-ID: <20260423105409.10371Da2-hca@linux.ibm.com> (raw)
In-Reply-To: <7b0e73e3c6f4000f9bf7cb161d8ca9a9f2312d70.1776264097.git.agordeev@linux.ibm.com>
On Wed, Apr 15, 2026 at 05:01:22PM +0200, Alexander Gordeev wrote:
> In various code paths, page_table_check_pte_clear() is called
> before converting a secure page, while in others it is called
> after. Make this consistent and always perform the conversion
> after the PTC hook has been called. Also make all conversion‑
> eligibility condition checks look the same, and rework the one
> in ptep_get_and_clear_full() slightly.
>
> Acked-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
> ---
> arch/s390/include/asm/pgtable.h | 39 +++++++++++++++------------------
> 1 file changed, 18 insertions(+), 21 deletions(-)
Why is this required for this series? It is anything but obvious to
me. If it is required please add some reasoning e.g. in the cover
letter or to the above changelog.
next prev parent reply other threads:[~2026-04-23 10:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 15:01 [PATCH v2 0/6] s390/mm: Batch PTE updates in lazy MMU mode Alexander Gordeev
2026-04-15 15:01 ` [PATCH v2 1/6] mm: Make lazy MMU mode context-aware Alexander Gordeev
2026-04-20 8:45 ` Kevin Brodsky
2026-04-21 4:57 ` Alexander Gordeev
2026-04-21 8:40 ` Kevin Brodsky
2026-04-21 14:12 ` David Hildenbrand (Arm)
2026-04-21 14:15 ` David Hildenbrand (Arm)
2026-04-21 14:25 ` Alexander Gordeev
2026-04-23 10:49 ` Heiko Carstens
2026-04-15 15:01 ` [PATCH v2 2/6] mm/pgtable: Fix bogus comment to clear_not_present_full_ptes() Alexander Gordeev
2026-04-16 7:58 ` David Hildenbrand (Arm)
2026-04-16 8:53 ` Alexander Gordeev
2026-04-15 15:01 ` [PATCH v2 3/6] s390/mm: Complete ptep_get() conversion Alexander Gordeev
2026-04-23 10:51 ` Heiko Carstens
2026-04-15 15:01 ` [PATCH v2 4/6] s390/mm: Make PTC and UV call order consistent Alexander Gordeev
2026-04-23 10:54 ` Heiko Carstens [this message]
2026-04-15 15:01 ` [PATCH v2 5/6] s390/mm: Batch PTE updates in lazy MMU mode Alexander Gordeev
2026-04-16 5:40 ` Heiko Carstens
2026-04-16 5:51 ` Alexander Gordeev
2026-04-23 12:28 ` Heiko Carstens
2026-04-15 15:01 ` [PATCH v2 6/6] s390/mm: Allow lazy MMU mode disabling Alexander Gordeev
2026-04-16 5:44 ` Heiko Carstens
2026-04-16 7:00 ` Alexander Gordeev
2026-04-16 8:22 ` Christian Borntraeger
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=20260423105409.10371Da2-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
/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