From: Mike Kravetz <mike.kravetz@oracle.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Miaohe Lin <linmiaohe@huawei.com>,
David Hildenbrand <david@redhat.com>,
Nadav Amit <nadav.amit@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Jann Horn <jannh@google.com>, John Hubbard <jhubbard@nvidia.com>,
James Houghton <jthoughton@google.com>,
Rik van Riel <riel@surriel.com>,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH v3 0/9] mm/hugetlb: Make huge_pte_offset() thread-safe for pmd unshare
Date: Fri, 9 Dec 2022 10:57:05 -0800 [thread overview]
Message-ID: <Y5OFAfYA9sNr3m6Q@monkey> (raw)
In-Reply-To: <20221209170100.973970-1-peterx@redhat.com>
On 12/09/22 12:00, Peter Xu wrote:
> Based on latest mm-unstable (dbccafc6e992).
>
> This can be seen as a follow-up series to Mike's recent hugetlb vma lock
> series for pmd unsharing, but majorly covering safe use of huge_pte_offset.
>
> Changelog for v2->v3:
> - Added a-bs and r-bs
> - In walk_hugetlb_range() hooks, don't release vma lock for cond_resched()
Thanks for your continued work on this Peter!
As a followup to that discussion about releasing vma lock for cond_resched(),
I do not have a strong opinion. Glad you kept my r-b.
--
Mike Kravetz
prev parent reply other threads:[~2022-12-09 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:00 Peter Xu
2022-12-09 17:00 ` [PATCH v3 1/9] mm/hugetlb: Let vma_offset_start() to return start Peter Xu
2022-12-09 17:00 ` [PATCH v3 2/9] mm/hugetlb: Don't wait for migration entry during follow page Peter Xu
2022-12-09 17:00 ` [PATCH v3 3/9] mm/hugetlb: Document huge_pte_offset usage Peter Xu
2022-12-09 17:00 ` [PATCH v3 4/9] mm/hugetlb: Move swap entry handling into vma lock when faulted Peter Xu
2022-12-09 17:00 ` [PATCH v3 5/9] mm/hugetlb: Make userfaultfd_huge_must_wait() safe to pmd unshare Peter Xu
2022-12-09 17:00 ` [PATCH v3 6/9] mm/hugetlb: Make hugetlb_follow_page_mask() " Peter Xu
2022-12-09 17:00 ` [PATCH v3 7/9] mm/hugetlb: Make follow_hugetlb_page() " Peter Xu
2022-12-09 17:00 ` [PATCH v3 8/9] mm/hugetlb: Make walk_hugetlb_range() " Peter Xu
2022-12-09 19:58 ` John Hubbard
2022-12-09 17:01 ` [PATCH v3 9/9] mm/hugetlb: Introduce hugetlb_walk() Peter Xu
2022-12-09 20:06 ` John Hubbard
2022-12-09 18:57 ` Mike Kravetz [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=Y5OFAfYA9sNr3m6Q@monkey \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=jhubbard@nvidia.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--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