linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>, Ye Liu <ye.liu@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ye Liu <liuye@kylinos.cn>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC RFC PATCH] mm: convert VM flags from macros to enum
Date: Mon, 13 Oct 2025 13:12:20 +0200	[thread overview]
Message-ID: <7ca0960f-9d1a-4ba4-b074-a6502578b82e@redhat.com> (raw)
In-Reply-To: <809f552d-3282-4746-ba49-066d2bd8d44f@lucifer.local>

On 13.10.25 13:04, Lorenzo Stoakes wrote:
> On Sat, Oct 11, 2025 at 05:30:52PM +0800, Ye Liu wrote:
>> From: Ye Liu <liuye@kylinos.cn>
>>
>> Hello MM maintainers and drgn community,
>>
>> This RFC proposes to convert VM_* flags from #define macros to enum
>> vm_flags. The motivation comes from recent drgn development where we
>> encountered difficulties in implementing VM flag parsing due to the
>> current macro-based approach.
> 
> This isn't going to work sorry, it's not valid to have flag values as an enum

I don't follow, can you elaborate? IIRC, the compiler will use an 
integer type to back the enum that will fit all values.

> (they're distinct) and also - importantly - I'm going to be making significant
> changes to VMA flags soon (to allow us to have arbitrary number of VMA flags on
> _all_ architectures as recently done with my series doing something similar with
> mm flags).

I guess this patch should not really make a big difference regarding 
your upcoming plans?

I do hate the enum stuff to make these tools happy, though :)

-- 
Cheers

David / dhildenb



  reply	other threads:[~2025-10-13 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11  9:30 Ye Liu
2025-10-13 11:04 ` Lorenzo Stoakes
2025-10-13 11:12   ` David Hildenbrand [this message]
2025-10-13 11:33     ` Lorenzo Stoakes
2025-10-13 12:31       ` David Hildenbrand
2025-10-13 12:33         ` David Hildenbrand
2025-10-13 12:57         ` Lorenzo Stoakes
2025-10-13 13:07           ` Vlastimil Babka
2025-10-13 13:19             ` Lorenzo Stoakes
2025-10-13 13:22               ` David Hildenbrand
2025-10-14  8:26               ` Ye Liu
2025-10-13 13:11           ` David Hildenbrand

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=7ca0960f-9d1a-4ba4-b074-a6502578b82e@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuye@kylinos.cn \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=ye.liu@linux.dev \
    /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