public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Peter Xu <peterx@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/2] userfaultfd: merge fs/userfaultfd.c into mm/userfaultfd.c
Date: Sat, 2 May 2026 06:38:53 +0200	[thread overview]
Message-ID: <afV_3ZZ69cpeYmpS@kernel.org> (raw)
In-Reply-To: <c2ecd0c6-fbb8-41f4-a7fb-2b1f15d1fa12@kernel.org>

On Fri, May 01, 2026 at 08:33:04PM +0200, David Hildenbrand (Arm) wrote:
> On 4/30/26 16:56, Mike Rapoport wrote:
> > On Thu, Apr 30, 2026 at 04:23:08PM +0200, David Hildenbrand (Arm) wrote:
> >> On 4/30/26 13:38, David Hildenbrand (Arm) wrote:
> >>>
> >>> Yeah, makes sense to me!
> >>>
> >>
> >> Thinking about this, is it reasonable that the kconfig stuff stays in fs/ ?
> > 
> > But it's in mm already.
> 
> $ grep HUGETLB fs/Kconfig
> config ARCH_SUPPORTS_HUGETLBFS
> menuconfig HUGETLBFS
>         depends on ARCH_SUPPORTS_HUGETLBFS
> if HUGETLBFS
> config HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON
>         depends on HUGETLB_PAGE_OPTIMIZE_VMEMMAP
> endif # HUGETLBFS
> config HUGETLB_PAGE
>         def_bool HUGETLBFS
> config HUGETLB_PAGE_OPTIMIZE_VMEMMAP
>         def_bool HUGETLB_PAGE
>         depends on ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP
>         select SPARSEMEM_VMEMMAP_PREINIT if ARCH_WANT_HUGETLB_VMEMMAP_PREINIT
> config HUGETLB_PMD_PAGE_TABLE_SHARING
>         def_bool HUGETLB_PAGE
> 

$ grep -c USERFAULT fs/Kconfig
0

HugeTLB is another story.
 
> -- 
> Cheers,
> David

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2026-05-02  4:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 11:35 [PATCH 0/2] userfaultfd: merge fs/userfaultfd.c into mm/userfaultfd.c Mike Rapoport
2026-04-30 11:35 ` [PATCH 1/2] " Mike Rapoport
2026-04-30 11:35 ` [PATCH 2/2] userfaultfd: make functions that are not used outside uffd static Mike Rapoport
2026-04-30 11:38 ` [PATCH 0/2] userfaultfd: merge fs/userfaultfd.c into mm/userfaultfd.c David Hildenbrand (Arm)
2026-04-30 14:23   ` David Hildenbrand (Arm)
2026-04-30 14:55     ` Mike Rapoport
2026-04-30 14:56     ` Mike Rapoport
2026-05-01 18:33       ` David Hildenbrand (Arm)
2026-05-02  4:38         ` Mike Rapoport [this message]
2026-05-02  6:37           ` David Hildenbrand (Arm)
2026-04-30 16:01 ` Andrew Morton
2026-05-01 14:57   ` Mike Rapoport

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=afV_3ZZ69cpeYmpS@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=david@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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