From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, akpm@linux-foundation.org,
rientjes@google.com, pjt@google.com, weixugc@google.com,
gthelen@google.com, mingo@redhat.com, corbet@lwn.net,
will@kernel.org, rppt@kernel.org, keescook@chromium.org,
tglx@linutronix.de, peterz@infradead.org, masahiroy@kernel.org,
samitolvanen@google.com, dave.hansen@linux.intel.com,
x86@kernel.org, frederic@kernel.org, hpa@zytor.com,
aneesh.kumar@linux.ibm.com
Subject: Re: [RFC 1/3] mm: ptep_clear() page table helper
Date: Wed, 17 Nov 2021 14:21:47 +0530 [thread overview]
Message-ID: <e461ba08-0aa8-e405-6383-5d921443135a@arm.com> (raw)
In-Reply-To: <20211116220038.116484-2-pasha.tatashin@soleen.com>
On 11/17/21 3:30 AM, Pasha Tatashin wrote:
> diff --git a/Documentation/vm/arch_pgtable_helpers.rst b/Documentation/vm/arch_pgtable_helpers.rst
> index 552567d863b8..fbe06ec75370 100644
> --- a/Documentation/vm/arch_pgtable_helpers.rst
> +++ b/Documentation/vm/arch_pgtable_helpers.rst
> @@ -66,9 +66,11 @@ PTE Page Table Helpers
> +---------------------------+--------------------------------------------------+
> | pte_mknotpresent | Invalidates a mapped PTE |
> +---------------------------+--------------------------------------------------+
> -| ptep_get_and_clear | Clears a PTE |
> +| ptep_clear | Clears a PTE |
> +---------------------------+--------------------------------------------------+
> -| ptep_get_and_clear_full | Clears a PTE |
> +| ptep_get_and_clear | Clears and returns PTE |
> ++---------------------------+--------------------------------------------------+
> +| ptep_get_and_clear_full | Clears and returns PTE (batched PTE unmap) |
> +---------------------------+--------------------------------------------------+
> | ptep_test_and_clear_young | Clears young from a PTE |
> +---------------------------+--------------------------------------------------+
Just curious. This does not have a corresponding change in mm/debug_vm_pgtable.c ?
next prev parent reply other threads:[~2021-11-17 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 22:00 [RFC 0/3] page table check Pasha Tatashin
2021-11-16 22:00 ` [RFC 1/3] mm: ptep_clear() page table helper Pasha Tatashin
2021-11-17 8:51 ` Anshuman Khandual [this message]
2021-11-17 16:43 ` Pasha Tatashin
2021-11-16 22:00 ` [RFC 2/3] mm: page table check Pasha Tatashin
2021-11-17 8:08 ` Jonathan Corbet
2021-11-17 16:47 ` Pasha Tatashin
2021-11-16 22:00 ` [RFC 3/3] x86: mm: add x86_64 support for " Pasha Tatashin
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=e461ba08-0aa8-e405-6383-5d921443135a@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=frederic@kernel.org \
--cc=gthelen@google.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--cc=x86@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: 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