From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "Gregory Price (Meta)" <gourry@gourry.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, akpm@linux-foundation.org,
david@kernel.org, liam@infradead.org, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com,
mgorman@techsingularity.net, mingo@kernel.org,
vschneid@redhat.com, kprateek.nayak@amd.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, nico.pache@linux.dev,
ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
lance.yang@linux.dev, usama.arif@linux.dev, kas@kernel.org,
joshua.hahnjy@gmail.com, rakie.kim@sk.com,
ying.huang@linux.alibaba.com, matthew.brost@intel.com,
byungchul@sk.com, apopple@nvidia.com, jannh@google.com,
pfalcato@suse.de, hannes@cmpxchg.org, osalvador@suse.de,
raghavendra.kt@amd.com
Subject: Re: [PATCH v5 6/7] mm: use BIT() for change_protection() flags
Date: Tue, 10 Nov 2026 15:16:59 +0000 [thread overview]
Message-ID: <avM1ZOdjf3w7yJjl@gremlin> (raw)
In-Reply-To: <20261110150446.2452975-7-gourry@gourry.net>
On Tue, Nov 10, 2026 at 10:04:45AM -0500, Gregory Price (Meta) wrote:
> The MM_CP_* flags are individual bits expressed as open-coded shifts.
> Use BIT() consistently for the complete block.
>
> No functional change intended.
>
> Suggested-by: David Hildenbrand <david@kernel.org>
> Link: https://lore.kernel.org/r/9b5e1573-6fd8-48a5-a274-a6e7ff83d2fe@kernel.org
> Assisted-by: LLM
> Acked-by: David Hildenbrand (Arm) <david@kernel.org>
> Signed-off-by: Gregory Price (Meta) <gourry@gourry.net>
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> include/linux/mm.h | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 55817dea7307f..da22750faddbd 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -3572,21 +3572,21 @@ int get_cmdline(struct task_struct *task, char *buffer, int buflen);
> * because something (e.g., COW, uffd-wp) blocks that from happening for all
> * PTEs automatically in a writable mapping.
> */
> -#define MM_CP_TRY_CHANGE_WRITABLE (1UL << 0)
> +#define MM_CP_TRY_CHANGE_WRITABLE BIT(0)
> /* Whether this protection change is for NUMA hints */
> -#define MM_CP_PROT_NUMA (1UL << 1)
> +#define MM_CP_PROT_NUMA BIT(1)
> /* Whether this change is for write protecting */
> -#define MM_CP_UFFD_WP (1UL << 2) /* do wp */
> -#define MM_CP_UFFD_WP_RESOLVE (1UL << 3) /* Resolve wp */
> +#define MM_CP_UFFD_WP BIT(2) /* do wp */
> +#define MM_CP_UFFD_WP_RESOLVE BIT(3) /* Resolve wp */
> #define MM_CP_UFFD_WP_ALL (MM_CP_UFFD_WP | \
> MM_CP_UFFD_WP_RESOLVE)
> /* Whether this change is for uffd RWP */
> -#define MM_CP_UFFD_RWP (1UL << 4) /* do rwp */
> -#define MM_CP_UFFD_RWP_RESOLVE (1UL << 5) /* resolve rwp */
> +#define MM_CP_UFFD_RWP BIT(4) /* do rwp */
> +#define MM_CP_UFFD_RWP_RESOLVE BIT(5) /* resolve rwp */
> #define MM_CP_UFFD_RWP_ALL (MM_CP_UFFD_RWP | \
> MM_CP_UFFD_RWP_RESOLVE)
> /* Whether a MM_CP_PROT_NUMA change is for promotion only */
> -#define MM_CP_PROT_NUMA_PROMO_ONLY (1UL << 6)
> +#define MM_CP_PROT_NUMA_PROMO_ONLY BIT(6)
>
> bool can_change_pte_writable(struct vm_area_struct *vma, unsigned long addr,
> pte_t pte);
> --
> 2.53.0-Meta
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-11-10 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:04 [PATCH v5 0/7] sched/numa: stop VMA scan filters from gating promotion Gregory Price (Meta)
2026-11-10 15:04 ` [PATCH v5 1/7] mm: support promotion-only NUMA hinting scans Gregory Price (Meta)
2026-11-10 15:04 ` [PATCH v5 2/7] mm: allow shared folios to be promoted to a fast tier Gregory Price (Meta)
2026-11-10 15:04 ` [PATCH v5 3/7] sched/numa: scan read-only file mappings in tiering mode Gregory Price (Meta)
2026-11-10 15:04 ` [PATCH v5 4/7] sched/numa: separate VMA placement from scan continuation Gregory Price (Meta)
2026-11-10 15:04 ` [PATCH v5 5/7] sched/numa: scan PID-inactive VMAs for promotion Gregory Price (Meta)
2026-11-10 15:04 ` [PATCH v5 6/7] mm: use BIT() for change_protection() flags Gregory Price (Meta)
2026-11-10 15:16 ` Lorenzo Stoakes (ARM) [this message]
2026-11-10 15:04 ` [PATCH v5 7/7] mm: use VMA flag helpers in NUMA balancing Gregory Price (Meta)
2026-11-10 15:15 ` Lorenzo Stoakes (ARM)
2026-11-10 16:24 ` Gregory Price (Meta)
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=avM1ZOdjf3w7yJjl@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bsegall@google.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=kprateek.nayak@amd.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=nico.pache@linux.dev \
--cc=osalvador@suse.de \
--cc=peterz@infradead.org \
--cc=pfalcato@suse.de \
--cc=raghavendra.kt@amd.com \
--cc=rakie.kim@sk.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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
all inboxes | Powered by JetHome®