From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Vineet Gupta <vgupta@synopsys.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: [PATCH V3 0/2] mm/debug_vm_pgtable: Some minor updates
Date: Wed, 20 Jan 2021 15:37:19 +0530 [thread overview]
Message-ID: <1611137241-26220-1-git-send-email-anshuman.khandual@arm.com> (raw)
This series contains some cleanups and new test suggestions from Catalin
from an earlier discussion.
https://lore.kernel.org/linux-mm/20201123142237.GF17833@gaia/
This series is based on v5.11-rc4 and has been tested on arm64, s390 and x86
but has only been build tested on riscv, arc etc. It would be great if folks
could test this on these platforms as well. Thank you.
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Cc: Vineet Gupta <vgupta@synopsys.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Changes in V3:
- Modified the comments for pxx_dirty(pxx_wrprotect(pxx)) tests per Steven
Changes in V2:
https://lore.kernel.org/linux-mm/1606825169-5229-1-git-send-email-anshuman.khandual@arm.com/
- Added some missing tests in pud_basic_tests()
- Added bidirectional dirty check after pxx_wrprotect() per Catalin
- Moved WARN_ON(pte_dirty(pte_wrprotect(pte))) just after page table entry creation
Changes in V1:
https://lore.kernel.org/linux-mm/1606453584-15399-1-git-send-email-anshuman.khandual@arm.com/
Anshuman Khandual (2):
mm/debug_vm_pgtable/basic: Add validation for dirtiness after write protect
mm/debug_vm_pgtable/basic: Iterate over entire protection_map[]
Documentation/vm/arch_pgtable_helpers.rst | 8 +--
mm/debug_vm_pgtable.c | 86 +++++++++++++++++++----
2 files changed, 78 insertions(+), 16 deletions(-)
--
2.20.1
next reply other threads:[~2021-01-20 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 10:07 Anshuman Khandual [this message]
2021-01-20 10:07 ` [PATCH V3 1/2] mm/debug_vm_pgtable/basic: Add validation for dirtiness after write protect Anshuman Khandual
2021-01-20 10:07 ` [PATCH V3 2/2] mm/debug_vm_pgtable/basic: Iterate over entire protection_map[] 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=1611137241-26220-1-git-send-email-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=gerald.schaefer@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=paul.walmsley@sifive.com \
--cc=vgupta@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.