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
Date: Tue, 26 Mar 2024 13:27:26 -0700 [thread overview]
Message-ID: <20240326132726.67e82559a928ac1636c8050c@linux-foundation.org> (raw)
In-Reply-To: <20240323151643.1047281-1-peterx@redhat.com>
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?
next prev parent reply other threads:[~2024-03-26 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 15:16 peterx
2024-03-23 17:39 ` Peter Xu
2024-03-25 13:05 ` Jason Gunthorpe
2024-03-26 20:27 ` Andrew Morton [this message]
2024-03-26 20:43 ` Peter Xu
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=20240326132726.67e82559a928ac1636c8050c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=sj@kernel.org \
--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