linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Roberts <ryan.roberts@arm.com>
To: Dev Jain <dev.jain@arm.com>,
	akpm@linux-foundation.org, david@redhat.com,
	catalin.marinas@arm.com, will@kernel.org
Cc: lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
	mhocko@suse.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, suzuki.poulose@arm.com,
	steven.price@arm.com, gshan@redhat.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Enable huge-vmalloc permission change
Date: Fri, 30 May 2025 11:03:34 +0100	[thread overview]
Message-ID: <adfe981a-ec9a-4051-a26f-91b691230161@arm.com> (raw)
In-Reply-To: <20250530090407.19237-1-dev.jain@arm.com>

On 30/05/2025 10:04, Dev Jain wrote:
> This series paves the path to enable huge mappings in vmalloc space by
> default on arm64. > For this we must ensure that we can handle any permission
> games on vmalloc space. 

And the linear map :)

> Currently, __change_memory_common() uses
> apply_to_page_range() which does not support changing permissions for
> leaf mappings. 

nit: A "leaf mapping" is the lowest level entry in the page tables for a given
address - i.e. it maps an address to some actual memory rather than to another
pgtable. It includes what the Arm ARM calls "page mappings" (PTE level) and
"block mappings" (PMD/PUD/.. level). apply_to_page_range() does support page
mappings, so saying it doesn't support leaf mappings is incorrect. It doesn't
support block mappings.

> We attempt to move away from this by using walk_page_range_novma(),
> similar to what riscv does right now; however, it is the responsibility
> of the caller to ensure that we do not pass a range, or split the range
> covering a partial leaf mapping.
> 
> This series is tied with Yang Shi's attempt [1] at using huge mappings
> in the linear mapping in case the system supports BBML2, in which case
> we will be able to split the linear mapping if needed without break-before-make.
> Thus, Yang's series, IIUC, will be one such user of my series; suppose we
> are changing permissions on a range of the linear map backed by PMD-hugepages,
> then the sequence of operations should look like the following:
> 
> split_range(start, (start + HPAGE_PMD_SIZE) & ~HPAGE_PMD_MASK);
> split_range(end & ~HPAGE_PMD_MASK, end);

I don't understand what the HPAGE_PMD_MASK twiddling is doing? That's not right.
It's going to give you the offset within the 2M region. You just want:

split_range(start)
split_range(end)

right?

> __change_memory_common(start, end);
> 
> However, this series can be used independently of Yang's; since currently
> permission games are being played only on pte mappings (due to apply_to_page_range
> not supporting otherwise), this series provides the mechanism for enabling
> huge mappings for various kernel mappings like linear map and vmalloc.

In other words, you are saying that this series is a prerequisite for Yang's
series (and both are prerequisites for huge vmalloc by default). Your series
adds a new capability that Yang's series will rely on (the ability to change
permissions on block mappings).

Thanks,
Ryan

> 
> [1] https://lore.kernel.org/all/20250304222018.615808-1-yang@os.amperecomputing.com/
> 
> Dev Jain (3):
>   mm: Allow pagewalk without locks
>   arm64: pageattr: Use walk_page_range_novma() to change memory
>     permissions
>   mm/pagewalk: Add pre/post_pte_table callback for lazy MMU on arm64
> 
>  arch/arm64/mm/pageattr.c | 81 +++++++++++++++++++++++++++++++++++++---
>  include/linux/pagewalk.h |  4 ++
>  mm/pagewalk.c            | 18 +++++++--
>  3 files changed, 94 insertions(+), 9 deletions(-)
> 



  parent reply	other threads:[~2025-05-30 10:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-30  9:04 Dev Jain
2025-05-30  9:04 ` [PATCH 1/3] mm: Allow pagewalk without locks Dev Jain
2025-05-30 10:33   ` Ryan Roberts
2025-05-30 21:33     ` Yang Shi
2025-05-30 10:57   ` Lorenzo Stoakes
2025-06-06  9:21     ` Dev Jain
2025-06-06  9:33       ` Dev Jain
2025-06-06 10:02       ` Lorenzo Stoakes
2025-05-30  9:04 ` [PATCH 2/3] arm64: pageattr: Use walk_page_range_novma() to change memory permissions Dev Jain
2025-05-30 12:53   ` Ryan Roberts
2025-06-02  4:35     ` Dev Jain
2025-06-06  9:49   ` Lorenzo Stoakes
2025-06-06 10:39     ` Dev Jain
2025-06-06 10:56       ` Lorenzo Stoakes
2025-06-06 11:08         ` Dev Jain
2025-06-09  9:41     ` Dev Jain
2025-06-09 11:00       ` Lorenzo Stoakes
2025-06-09 11:31         ` Dev Jain
2025-05-30  9:04 ` [PATCH 3/3] mm/pagewalk: Add pre/post_pte_table callback for lazy MMU on arm64 Dev Jain
2025-05-30 11:14   ` Lorenzo Stoakes
2025-05-30 12:12     ` Ryan Roberts
2025-05-30 12:18       ` Lorenzo Stoakes
2025-05-30  9:24 ` [PATCH 0/3] Enable huge-vmalloc permission change Dev Jain
2025-05-30 10:03 ` Ryan Roberts [this message]
2025-05-30 10:10   ` Dev Jain
2025-05-30 10:37     ` Ryan Roberts
2025-05-30 10:42       ` Dev Jain
2025-05-30 10:51         ` Ryan Roberts
2025-05-30 11:11           ` Dev Jain

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=adfe981a-ec9a-4051-a26f-91b691230161@arm.com \
    --to=ryan.roberts@arm.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=gshan@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=steven.price@arm.com \
    --cc=surenb@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=vbabka@suse.cz \
    --cc=will@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