From: David Hildenbrand <david@redhat.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
inuxppc-dev@lists.ozlabs.org, linux-ia64@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Naoya Horiguchi <naoya.horiguchi@linux.dev>,
Michael Ellerman <mpe@ellerman.id.au>,
Muchun Song <songmuchun@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH] hugetlb: simplify hugetlb handling in follow_page_mask
Date: Fri, 2 Sep 2022 20:52:44 +0200 [thread overview]
Message-ID: <323fdb0f-c5a5-e0e5-1ff4-ab971bc295cc@redhat.com> (raw)
In-Reply-To: <YxJQfGSsbXd3W4m/@monkey>
>>> Adding Christophe on Cc:
>>>
>>> Christophe do you know if is_hugepd is true for all hugetlb entries, not
>>> just hugepd?
>>>
>>> On systems without hugepd entries, I guess ptdump skips all hugetlb entries.
>>> Sigh!
>>
>> IIUC, the idea of ptdump_walk_pgd() is to dump page tables even outside
>> VMAs (for debugging purposes?).
>>
>> I cannot convince myself that that's a good idea when only holding the
>> mmap lock in read mode, because we can just see page tables getting
>> freed concurrently e.g., during concurrent munmap() ... while holding
>> the mmap lock in read we may only walk inside VMA boundaries.
>>
>> That then raises the questions if we're only calling this on special MMs
>> (e.g., init_mm) whereby we cannot really see concurrent munmap() and
>> where we shouldn't have hugetlb mappings or hugepd entries.
>>
>
> This is going to require a little more thought.
>
> Since Baolin's patch for stable releases is moving forward, I want to
> get the cleanup provided by this patch in ASAP. So, I am going to rebase
> this patch on Baolin's with the other fixups.
>
> Will come back to this cleanup later.
Sure, no need to do it all at once (I was just bringing it up while
thinking about it).
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-09-02 18:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:40 [PATCH] hugetlb: simplify hugetlb handling in follow_page_mask Mike Kravetz
2022-08-30 1:06 ` Baolin Wang
2022-08-30 16:44 ` Mike Kravetz
2022-08-30 18:39 ` Mike Kravetz
2022-08-31 1:07 ` Baolin Wang
2022-09-01 0:00 ` Mike Kravetz
2022-09-01 1:24 ` Baolin Wang
2022-09-01 6:59 ` David Hildenbrand
2022-09-01 10:40 ` Baolin Wang
2022-08-30 8:11 ` David Hildenbrand
2022-08-30 16:52 ` Mike Kravetz
2022-08-30 21:31 ` Mike Kravetz
2022-08-31 8:07 ` David Hildenbrand
2022-09-02 18:50 ` Mike Kravetz
2022-09-02 18:52 ` David Hildenbrand [this message]
2022-09-03 6:59 ` Christophe Leroy
2022-09-03 7:07 ` Christophe Leroy
2022-09-04 11:49 ` Michael Ellerman
2022-09-05 8:37 ` David Hildenbrand
2022-09-05 9:33 ` Christophe Leroy
2022-09-05 9:46 ` David Hildenbrand
2022-09-05 16:05 ` Christophe Leroy
2022-09-05 16:09 ` David Hildenbrand
2022-08-31 5:08 ` kernel test robot
2022-08-31 20:42 ` Mike Kravetz
2022-09-01 16:19 ` Mike Kravetz
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=323fdb0f-c5a5-e0e5-1ff4-ab971bc295cc@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=christophe.leroy@csgroup.eu \
--cc=inuxppc-dev@lists.ozlabs.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=naoya.horiguchi@linux.dev \
--cc=songmuchun@bytedance.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;
as well as URLs for NNTP newsgroup(s).