From: Muhammad Usama Anjum <usama.anjum@arm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: usama.anjum@arm.com, linux-s390@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-sparse@vger.kernel.org,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Chris Li <sparse@chrisli.org>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [RFC PATCH 0/4] mm: introduce __ptent sparse attribute
Date: Mon, 20 Jul 2026 14:49:33 +0100 [thread overview]
Message-ID: <e98b0529-4f70-4e69-8d71-7b89f20cad10@arm.com> (raw)
In-Reply-To: <e50fb51d-72ac-4ace-b532-5cf32ecd80f1@kernel.org>
On 17/07/2026 3:53 pm, David Hildenbrand (Arm) wrote:
> On 7/17/26 14:32, Alexander Gordeev wrote:
>> Hi All!
>>
>> This RFC is a result the implementation of lazy MMU mode on s390 [1].
>>
>> Heiko Carstens requested some mechanism that would rule out direct
>> dereferencing of PTE pointers, which otherwise would bypass the per-
>> cpu cache on s390 and lead to catastrophic results.
This is the exact point we want to fix once and for all. Please feel free
to review and endorse the approach we are going with on the original discussion.
> There is some information here:
>
> https://lore.kernel.org/r/6110202c-057b-4701-8c04-1a76ee7bb9ab@arm.com
--
Thanks,
Usama
prev parent reply other threads:[~2026-07-20 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:32 [RFC PATCH 0/4] mm: introduce __ptent sparse attribute Alexander Gordeev
2026-07-17 13:32 ` [RFC PATCH 1/4] mm: use proper PTE accessors in madvise() and mremap() Alexander Gordeev
2026-07-17 17:14 ` Kevin Brodsky
2026-07-17 13:32 ` [RFC PATCH 2/4] mm: introduce ptep_get_nopgtable() and set_pte_nopgtable() accessors Alexander Gordeev
2026-07-17 13:32 ` [RFC PATCH 3/4] mm: introduce __ptent sparse attribute Alexander Gordeev
2026-07-17 13:32 ` [RFC PATCH 4/4] s390/mm: implement __ptent-aware pte_t type Alexander Gordeev
2026-07-17 14:53 ` [RFC PATCH 0/4] mm: introduce __ptent sparse attribute David Hildenbrand (Arm)
2026-07-20 13:49 ` Muhammad Usama Anjum [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=e98b0529-4f70-4e69-8d71-7b89f20cad10@arm.com \
--to=usama.anjum@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hca@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 \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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