From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, anshuman.khandual@arm.com,
songmuchun@bytedance.com, akpm@linux-foundation.org
Subject: + arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64-fix.patch added to -mm tree
Date: Thu, 14 Apr 2022 14:00:12 -0700 [thread overview]
Message-ID: <20220414210013.47D79C385A1@smtp.kernel.org> (raw)
The patch titled
Subject: arm64: mm: hugetlb: restructure the code comment inside flush_dcache_page()
has been added to the -mm tree. Its filename is
arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64-fix.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64-fix.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64-fix.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Muchun Song <songmuchun@bytedance.com>
Subject: arm64: mm: hugetlb: restructure the code comment inside flush_dcache_page()
Restructure the code comment inside flush_dcache_page() to make it more
clear.
Link: https://lkml.kernel.org/r/20220414072646.21910-1-songmuchun@bytedance.com
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/arch/arm64/mm/flush.c~arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64-fix
+++ a/arch/arm64/mm/flush.c
@@ -81,9 +81,10 @@ void flush_dcache_page(struct page *page
* read-only when CONFIG_HUGETLB_PAGE_FREE_VMEMMAP is enabled (more
* details can refer to vmemmap_remap_pte()). Although
* __sync_icache_dcache() only set PG_dcache_clean flag on the head
- * page struct, some tail page structs still can be seen the flag is
- * set since the head vmemmap page frame is reused (more details can
- * refer to the comments above page_fixed_fake_head()).
+ * page struct, there is more than one page struct with PG_dcache_clean
+ * associated with the HugeTLB page since the head vmemmap page frame
+ * is reused (more details can refer to the comments above
+ * page_fixed_fake_head()).
*/
if (hugetlb_free_vmemmap_enabled() && PageHuge(page))
page = compound_head(page);
_
Patches currently in -mm which might be from songmuchun@bytedance.com are
mm-hugetlb_vmemmap-introduce-arch_want_hugetlb_page_free_vmemmap.patch
arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64.patch
arm64-mm-hugetlb-enable-hugetlb_page_free_vmemmap-for-arm64-fix.patch
mm-hugetlb_vmemmap-cleanup-hugetlb_vmemmap-related-functions.patch
mm-hugetlb_vmemmap-cleanup-hugetlb_free_vmemmap_enabled.patch
mm-hugetlb_vmemmap-cleanup-config_hugetlb_page_free_vmemmap.patch
mm-rmap-fix-cache-flush-on-thp-pages.patch
dax-fix-cache-flush-on-pmd-mapped-pages.patch
mm-rmap-introduce-pfn_mkclean_range-to-cleans-ptes.patch
mm-pvmw-add-support-for-walking-devmap-pages.patch
dax-fix-missing-writeprotect-the-pte-entry.patch
mm-simplify-follow_invalidate_pte.patch
reply other threads:[~2022-04-14 21:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220414210013.47D79C385A1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.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