linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Replace READ_ONCE() with standard page table accessors
Date: Tue, 7 Oct 2025 15:23:23 +0530	[thread overview]
Message-ID: <c26dbbf7-8475-4424-8e73-b35a845a2949@arm.com> (raw)
In-Reply-To: <627da4d5-5c6b-4bf4-9544-9021062d378e@arm.com>


On 07/10/25 1:24 pm, Anshuman Khandual wrote:
>
> On 07/10/25 12:41 PM, Dev Jain wrote:
>> On 07/10/25 12:01 pm, Anshuman Khandual wrote:
>>> Replace all READ_ONCE() with a standard page table accessors i.e pxdp_get()
>>> that defaults into READ_ONCE() in cases where platform does not override.
>> Does any platform override into something else currently? The way you write
>> the description implies that.
> That's how the callbacks have been designed to be overridden when required.

What I mean is, if currently some arch is overriding into something else,
this patch will be a functional change. So it is beneficial to say
in the description that the patch is a safeguard for when the platform
chooses to override, and no functional change is intended.

Reviewed-by: Dev Jain <dev.jain@arm.com>

>>


  reply	other threads:[~2025-10-07  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  6:31 Anshuman Khandual
2025-10-07  7:11 ` Dev Jain
2025-10-07  7:54   ` Anshuman Khandual
2025-10-07  9:53     ` Dev Jain [this message]
2025-10-07  8:47 ` David Hildenbrand
2025-10-09 11:35 ` Lance Yang
2025-10-10  1:18 ` Wei Yang

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=c26dbbf7-8475-4424-8e73-b35a845a2949@arm.com \
    --to=dev.jain@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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