linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: jane.chu@oracle.com
To: David Hildenbrand <david@redhat.com>,
	harry.yoo@oracle.com, osalvador@suse.de, liushixin2@huawei.com,
	muchun.song@linux.dev, akpm@linux-foundation.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: fix copy_hugetlb_page_range() to use ->pt_share_count
Date: Thu, 11 Sep 2025 12:54:36 -0700	[thread overview]
Message-ID: <2fa7aa11-6521-40f3-9934-aba275154ca2@oracle.com> (raw)
In-Reply-To: <e9b34151-0879-4900-af9f-2ce0dbb678a6@redhat.com>


On 9/9/2025 11:45 PM, David Hildenbrand wrote:
[..]
>> -        /*
>> -         * If the pagetables are shared don't copy or take references.
>> -         *
>> -         * dst_pte == src_pte is the common case of src/dest sharing.
>> -         * However, src could have 'unshared' and dst shares with
>> -         * another vma. So page_count of ptep page is checked instead
>> -         * to reliably determine whether pte is shared.
>> -         */
>> -        if (page_count(virt_to_page(dst_pte)) > 1) {
>> +#ifdef CONFIG_HUGETLB_PMD_PAGE_TABLE_SHARING
>> +        /* If the pagetables are shared don't copy or take 
>> references. */
> 
> Why remove so much of the original comment?

Because, this part of checking has already advanced from the "dst_pte == 
src_pte" to "page_count() > 1" to ->pt_share_count > 0, it seems cleaner 
to just keep an one liner comment.
That said, if you feel the comments should be kept, I'd be happy to 
restore them with a bit revision.

> 
>> +        if (ptdesc_pmd_pts_count(virt_to_ptdesc(dst_pte)) > 0) {
>>               addr |= last_addr_mask;
>>               continue;
>>           }
> 
> LGTM, thanks!

Thanks!
-jane

> 




  reply	other threads:[~2025-09-11 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 18:43 Jane Chu
2025-09-10  1:14 ` Harry Yoo
2025-09-10 19:23   ` jane.chu
2025-09-10  6:45 ` David Hildenbrand
2025-09-11 19:54   ` jane.chu [this message]
2025-09-12  7:31     ` David Hildenbrand
2025-09-15 16:51       ` jane.chu

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=2fa7aa11-6521-40f3-9934-aba275154ca2@oracle.com \
    --to=jane.chu@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=harry.yoo@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liushixin2@huawei.com \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    /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