From: Johannes Weiner <hannes@cmpxchg.org>
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Alistair Popple <apopple@nvidia.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Nadav Amit <nadav.amit@gmail.com>
Subject: Re: [PATCH] mm/uffd: Move USERFAULTFD configs into mm/
Date: Wed, 20 Apr 2022 11:31:29 -0400 [thread overview]
Message-ID: <YmAnUQdQ63jD48ad@cmpxchg.org> (raw)
In-Reply-To: <20220420144823.35277-1-peterx@redhat.com>
On Wed, Apr 20, 2022 at 10:48:23AM -0400, Peter Xu wrote:
> We used to have USERFAULTFD configs stored in init/. It makes sense as a
> start because that's the default place for storing syscall related configs.
>
> However userfaultfd evolved a bit in the past few years and some more
> config options were added. They're no longer related to syscalls and start
> to be not suitable to be kept in the init/ directory anymore, because
> they're pure mm concepts.
>
> But it's not ideal either to keep the userfaultfd configs separate from
> each other. Hence this patch moves the userfaultfd configs under init/ to
> be under mm/ so that we'll start to group all userfaultfd configs
> together.
>
> We do have quite a few examples of syscall related configs that are not put
> under init/Kconfig: FTRACE_SYSCALLS, SWAP, FILE_LOCKING, MEMFD_CREATE..
> They all reside in the dir where they're more suitable for the concept. So
> it seems there's no restriction to keep the role of having syscall related
> CONFIG_* under init/ only.
>
> Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
next prev parent reply other threads:[~2022-04-20 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:48 Peter Xu
2022-04-20 15:31 ` Johannes Weiner [this message]
2022-04-20 16:46 ` Axel Rasmussen
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=YmAnUQdQ63jD48ad@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.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