From: Zi Yan <ziy@nvidia.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: thp: fix wrong cache flush in remove_migration_pmd()
Date: Fri, 21 Jan 2022 09:55:06 -0500 [thread overview]
Message-ID: <22BE9A5D-5777-4BE3-9F2C-F5A722E4F4AA@nvidia.com> (raw)
In-Reply-To: <20220121081345.80320-1-songmuchun@bytedance.com>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
On 21 Jan 2022, at 3:13, Muchun Song wrote:
> The flush_cache_page() is supposed to be justified only if the page
> is already placed in process page table, and that is done right after
> flush_cache_page(). So using this interface is wrong. And there is
> no need to invalite cache since it was non-present before in
> remove_migration_pmd(). So just to remove it.
>
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> ---
> mm/huge_memory.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index f58524394dc1..45ede45b11f5 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -3207,7 +3207,6 @@ void remove_migration_pmd(struct page_vma_mapped_walk *pvmw, struct page *new)
> if (pmd_swp_uffd_wp(*pvmw->pmd))
> pmde = pmd_wrprotect(pmd_mkuffd_wp(pmde));
>
> - flush_cache_range(vma, mmun_start, mmun_start + HPAGE_PMD_SIZE);
> if (PageAnon(new))
> page_add_anon_rmap(new, vma, mmun_start, true);
> else
> @@ -3215,6 +3214,8 @@ void remove_migration_pmd(struct page_vma_mapped_walk *pvmw, struct page *new)
> set_pmd_at(mm, mmun_start, pvmw->pmd, pmde);
> if ((vma->vm_flags & VM_LOCKED) && !PageDoubleMap(new))
> mlock_vma_page(new);
> +
> + /* No need to invalidate - it was non-present before */
> update_mmu_cache_pmd(vma, address, pvmw->pmd);
> }
> #endif
LGTM. Thanks. Reviewed-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
prev parent reply other threads:[~2022-01-21 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 8:13 Muchun Song
2022-01-21 8:13 ` [PATCH 2/2] mm: fix missing cache flush for all tail pages of THP Muchun Song
2022-01-21 14:59 ` Zi Yan
2022-01-21 22:25 ` Muchun Song
2022-01-21 14:55 ` Zi Yan [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=22BE9A5D-5777-4BE3-9F2C-F5A722E4F4AA@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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