From: John Hubbard <jhubbard@nvidia.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, <linux-mm@kvack.org>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
David Rientjes <rientjes@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Mel Gorman <mgorman@techsingularity.net>,
Mike Rapoport <rppt@linux.ibm.com>,
"Dan Williams" <dan.j.williams@intel.com>,
Pavel Tatashin <pavel.tatashin@microsoft.com>,
Matthew Wilcox <willy@infradead.org>,
"David Hildenbrand" <david@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] mm/page_alloc: Add alloc_contig_pages()
Date: Thu, 17 Oct 2019 22:03:31 -0700 [thread overview]
Message-ID: <0709de85-05f4-2a9d-e346-bd15b10e5a1a@nvidia.com> (raw)
In-Reply-To: <1b173827-b08c-b294-bf86-22228bdfd542@arm.com>
On 10/17/19 8:28 PM, Anshuman Khandual wrote:
> On 10/18/2019 02:44 AM, John Hubbard wrote:
>> On 10/17/19 1:24 AM, Anshuman Khandual wrote:
...
> Yeah, it is bit non-trivial because v5 of the pgtable tests are still
> on the latest linux-next (20191015 or 20191017). You will need to
> revert the following patches.
>
> 1. mm/hugetlb: make alloc_gigantic_page() available for general use
> 2. mm/debug: add tests validating architecture page table helpers
> 3. mm-debug-add-tests-validating-architecture-page-table-helpers-fix
>
> and apply the following patch (https://patchwork.kernel.org/patch/11190213/)
>
> 1. hugetlbfs: don't access uninitialized memmaps in pfn_range_valid_gigantic()
>
> After which this particular patch here will apply cleanly. Hope this helps.
>
Yes, that helps, I wouldn't have worked that out on my own. :)
I'm not sure if I'll have anything to add, but I do want to take a peek,
so I can try to keep up with how huge pages are evolving.
thanks,
John Hubbard
NVIDIA
prev parent reply other threads:[~2019-10-18 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1571300646-32240-1-git-send-email-anshuman.khandual@arm.com>
2019-10-17 21:14 ` John Hubbard
[not found] ` <1b173827-b08c-b294-bf86-22228bdfd542@arm.com>
2019-10-18 5:03 ` John Hubbard [this message]
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=0709de85-05f4-2a9d-e346-bd15b10e5a1a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=pavel.tatashin@microsoft.com \
--cc=rientjes@google.com \
--cc=rppt@linux.ibm.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