Received-SPF: pass (google.com: domain of linux-kernel+bounces-119911-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Tue, 26 Mar 2024 13:27:26 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: peterx@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, SeongJae Park
 <sj@kernel.org>, Jason Gunthorpe <jgg@nvidia.com>, Mike Rapoport
 <rppt@kernel.org>, Matthew Wilcox <willy@infradead.org>, kernel test robot
 <lkp@intel.com>
Subject: Re: [PATCH] mm/arch: Provide pud_pfn() fallback
Message-Id: <20240326132726.67e82559a928ac1636c8050c@linux-foundation.org>
In-Reply-To: <20240323151643.1047281-1-peterx@redhat.com>
References: <20240323151643.1047281-1-peterx@redhat.com>
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sat, 23 Mar 2024 11:16:43 -0400 peterx@redhat.com wrote:

> From: Peter Xu <peterx@redhat.com>
> 
> The comment in the code explains the reasons.  We took a different approach
> comparing to pmd_pfn() by providing a fallback function.
> 
> Another option is to provide some lower level config options (compare to
> HUGETLB_PAGE or THP) to identify which layer an arch can support for such
> huge mappings.  However that can be an overkill.
> 
> ...
>
> If we care about per-commit build errors (and if it is ever feasible to
> reorder), we can move this patch to be before the patch "mm/gup: handle
> huge pud for follow_pud_mask()" in mm-unstable to unbreak build on that
> commit.

I temporarily disabled that whole series a few days ago.  Because of
multiple build issues, iirc.

Let's make that permanent.  Please redo the whole series against
mm-unstable and resend?