From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
SeongJae Park <sj@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] mm: move mmap/vma locking logic into specific files
Date: Wed, 16 Apr 2025 08:32:25 +0100 [thread overview]
Message-ID: <e98bfbad-2aa5-418d-b3ca-019a3f509afe@lucifer.local> (raw)
In-Reply-To: <CAJuCfpEEOh3igTGir-UxJLfKr+y2p5xDinZR9JDLg6AzO5Dw8Q@mail.gmail.com>
On Tue, Apr 15, 2025 at 09:07:54AM -0700, Suren Baghdasaryan wrote:
[snip]
> > #ifdef CONFIG_MMU
> > #ifdef CONFIG_LOCK_MM_AND_FIND_VMA
> > // MMU version of lock_mm_and_find_vma() and helpers
> > #endif /* CONFIG_LOCK_MM_AND_FIND_VMA */
> > #else /* CONFIG_MMU */
> > // NOMMU version of lock_mm_and_find_vma()
> > #endif /* CONFIG_MMU */
> >
> > Note that CONFIG_PER_VMA_LOCK already depends on CONFIG_NOMMU.
>
> I meant to say CONFIG_PER_VMA_LOCK already depends on CONFIG_MMU :)
>
Haha ack :)
[snip]
next prev parent reply other threads:[~2025-04-16 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 13:10 [PATCH 0/2] separate out mmap_lock/VMA locking and update MAINTAINERS Lorenzo Stoakes
2025-04-15 13:10 ` [PATCH 1/2] mm: move mmap/vma locking logic into specific files Lorenzo Stoakes
2025-04-15 16:06 ` Suren Baghdasaryan
2025-04-15 16:07 ` Suren Baghdasaryan
2025-04-16 7:32 ` Lorenzo Stoakes [this message]
2025-04-15 17:58 ` Paul E. McKenney
2025-04-16 7:31 ` Lorenzo Stoakes
2025-04-16 7:30 ` Lorenzo Stoakes
2025-04-15 13:10 ` [PATCH 2/2] MAINTAINERS: add section for locking of mm's and VMAs Lorenzo Stoakes
2025-04-15 13:25 ` David Hildenbrand
2025-04-16 7:33 ` Lorenzo Stoakes
2025-04-16 8:07 ` David Hildenbrand
2025-04-15 15:37 ` Liam R. Howlett
2025-04-15 15:43 ` Lorenzo Stoakes
2025-04-15 16:14 ` Suren Baghdasaryan
2025-04-16 7:36 ` Lorenzo Stoakes
2025-04-15 18:00 ` Shakeel Butt
2025-04-16 6:47 ` Lorenzo Stoakes
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=e98bfbad-2aa5-418d-b3ca-019a3f509afe@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@kernel.org \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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