LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com> To: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org, anshuman.khandual@arm.com, gerald.schaefer@linux.ibm.com, aneesh.kumar@linux.ibm.com, christophe.leroy@csgroup.eu, cai@lca.pw, catalin.marinas@arm.com, will@kernel.org, vgupta@synopsys.com, akpm@linux-foundation.org, chuhu@redhat.com, shan.gavin@gmail.com Subject: [PATCH v5 00/12] mm/debug_vm_pgtable: Enhancements Date: Mon, 2 Aug 2021 14:04:07 +0800 [thread overview] Message-ID: <20210802060419.1360913-1-gshan@redhat.com> (raw) There are couple of issues with current implementations and this series tries to resolve the issues: (a) All needed information are scattered in variables, passed to various test functions. The code is organized in pretty much relaxed fashion. (b) The page isn't allocated from buddy during page table entry modifying tests. The page can be invalid, conflicting to the implementations of set_xxx_at() on ARM64. The target page is accessed so that the iCache can be flushed when execution permission is given on ARM64. Besides, the target page can be unmapped and accessing to it causes kernel crash. "struct pgtable_debug_args" is introduced to address issue (a). For issue (b), the used page is allocated from buddy in page table entry modifying tests. The corresponding tets will be skipped if we fail to allocate the (huge) page. For other test cases, the original page around to kernel symbol (@start_kernel) is still used. The patches are organized as below. PATCH[2-10] could be combined to one patch, but it will make the review harder: PATCH[1] introduces "struct pgtable_debug_args" as place holder of all needed information. With it, the old and new implementation can coexist. PATCH[2-10] uses "struct pgtable_debug_args" in various test functions. PATCH[11] removes the unused code for old implementation. PATCH[12] fixes the issue of corrupted page flag for ARM64 Changelog ========= v5: * Pick r-bs from Anshuman and rebase to 5.14.rc4 (Gavin) * Use args->start_p4dp to free p4d entries (Anshuman) * Introduce helper to allocate huge page in init_arg() (Anshuman) * Bail early if the allocated page doesn't exist in swap_migration_tests() and correct the comments (Anshuman) * Add fixes tag to PATCH[v4 12/12] (Christophe) * Address misc comments (Anshuman) v4: * Determine the page allocation method according to MAX_ORDER (Anshuman) * Move existing comments to init_args() (Anshuman) * Code refactoring as suggested by Anshuman (Anshuman) * Improved commit log and add comments for flush_dcache_page() in PATCH[v4 12/12] (Anshuman) * Address misc comments (Anshuman) v3: * Fix the warning caused by allocating more pages than (1 << (MAX_ORDER - 1)) in init_args() (syzbot) * Fix build warning by dropping unused variables in separate patches (0-day) * Missed "WARN_ON(!pud_none(pud))" in pud_huge_tests() in PATCH[v2 09/12] (0-day) * Fix the subjects for PATCH[05/12] and PATCH[09/12] (Gavin) v2: * Rename struct vm_pgtable_debug to struct pgtable_debug_args. The parameter name to various test functions are renamed to "@args" (Anshuman) * Code changes as suggested by Anshuman (Anshuman) Gavin Shan (12): mm/debug_vm_pgtable: Introduce struct pgtable_debug_args mm/debug_vm_pgtable: Use struct pgtable_debug_args in basic tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in leaf and savewrite tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in protnone and devmap tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in soft_dirty and swap tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in migration and thp tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PTE modifying tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PMD modifying tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PUD modifying tests mm/debug_vm_pgtable: Use struct pgtable_debug_args in PGD and P4D modifying tests mm/debug_vm_pgtable: Remove unused code mm/debug_vm_pgtable: Fix corrupted page flag mm/debug_vm_pgtable.c | 916 +++++++++++++++++++++++++----------------- 1 file changed, 558 insertions(+), 358 deletions(-) -- 2.23.0
next reply other threads:[~2021-08-02 6:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 6:04 Gavin Shan [this message] 2021-08-02 6:04 ` [PATCH v5 01/12] mm/debug_vm_pgtable: Introduce struct pgtable_debug_args Gavin Shan 2021-08-03 4:42 ` Anshuman Khandual 2021-08-03 5:22 ` Gavin Shan 2021-08-02 6:04 ` [PATCH v5 02/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in basic tests Gavin Shan 2021-08-02 6:04 ` [PATCH v5 03/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in leaf and savewrite tests Gavin Shan 2021-08-02 6:04 ` [PATCH v5 04/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in protnone and devmap tests Gavin Shan 2021-08-02 6:04 ` [PATCH v5 05/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in soft_dirty and swap tests Gavin Shan 2021-08-02 6:04 ` [PATCH v5 06/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in migration and thp tests Gavin Shan 2021-08-02 6:04 ` [PATCH v5 07/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in PTE modifying tests Gavin Shan 2021-08-02 6:04 ` [PATCH v5 08/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in PMD " Gavin Shan 2021-08-02 6:04 ` [PATCH v5 09/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in PUD " Gavin Shan 2021-08-02 6:04 ` [PATCH v5 10/12] mm/debug_vm_pgtable: Use struct pgtable_debug_args in PGD and P4D " Gavin Shan 2021-08-02 6:04 ` [PATCH v5 11/12] mm/debug_vm_pgtable: Remove unused code Gavin Shan 2021-08-02 6:04 ` [PATCH v5 12/12] mm/debug_vm_pgtable: Fix corrupted page flag Gavin Shan 2021-08-03 6:50 ` [PATCH v5 00/12] mm/debug_vm_pgtable: Enhancements Anshuman Khandual
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=20210802060419.1360913-1-gshan@redhat.com \ --to=gshan@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=aneesh.kumar@linux.ibm.com \ --cc=anshuman.khandual@arm.com \ --cc=cai@lca.pw \ --cc=catalin.marinas@arm.com \ --cc=christophe.leroy@csgroup.eu \ --cc=chuhu@redhat.com \ --cc=gerald.schaefer@linux.ibm.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=shan.gavin@gmail.com \ --cc=vgupta@synopsys.com \ --cc=will@kernel.org \ /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: linkBe 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).