From: Kevin Brodsky <kevin.brodsky@arm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: [RFC PATCH 1/2] mm: make lazy MMU mode context-aware
Date: Tue, 14 Apr 2026 19:38:13 +0200 [thread overview]
Message-ID: <d5a39861-0f5f-4aee-84e3-f4d956f83461@arm.com> (raw)
In-Reply-To: <384c5b93-7939-4a9e-9298-66397cc6fa28-agordeev@linux.ibm.com>
On 14/04/2026 18:08, Alexander Gordeev wrote:
> On Tue, Apr 14, 2026 at 04:30:10PM +0200, Kevin Brodsky wrote:
>>> * @mm: Address space the ptes represent.
>> Not sure that makes sense, maybe something like "Address space the PTEs
>> belong to"?
>>
>>> * @addr: Address of the first pte.
>> Isn't it the address of the underlying memory rather?
> Will update both and also the clear_not_present_full_ptes()
> comment, where I copied it from.
Oh I hadn't realised those comments came from there, that would be nice,
thanks. A better reference might be a function like clear_ptes(), which
was probably the inspiration for clear_not_present_full_ptes() (but
wording adjustments were needed for the latter since the PTEs don't
point to any memory).
- Kevin
next prev parent reply other threads:[~2026-04-14 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 7:41 [RFC PATCH 0/2] s390/mm: Batch PTE updates in lazy MMU mode Alexander Gordeev
2026-03-25 7:41 ` [RFC PATCH 1/2] mm: make lazy MMU mode context-aware Alexander Gordeev
2026-03-25 9:55 ` David Hildenbrand (Arm)
2026-03-25 16:20 ` Alexander Gordeev
2026-03-25 16:37 ` Alexander Gordeev
2026-03-31 14:15 ` Kevin Brodsky
2026-04-11 9:31 ` Alexander Gordeev
2026-04-13 10:01 ` Kevin Brodsky
2026-03-31 21:11 ` David Hildenbrand (Arm)
2026-04-13 13:43 ` Alexander Gordeev
2026-04-13 18:32 ` David Hildenbrand (Arm)
2026-04-14 7:53 ` Alexander Gordeev
2026-04-14 8:11 ` David Hildenbrand (Arm)
2026-04-14 14:30 ` Kevin Brodsky
2026-04-14 16:08 ` Alexander Gordeev
2026-04-14 17:38 ` Kevin Brodsky [this message]
2026-03-25 7:41 ` [RFC PATCH 2/2] s390/mm: Batch PTE updates in lazy MMU mode Alexander Gordeev
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=d5a39861-0f5f-4aee-84e3-f4d956f83461@arm.com \
--to=kevin.brodsky@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=ryan.roberts@arm.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