linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, pjt@google.com, weixugc@google.com,
	gthelen@google.com, mingo@redhat.com, will@kernel.org,
	rppt@kernel.org, dave.hansen@linux.intel.com, hpa@zytor.com,
	aneesh.kumar@linux.ibm.com, jirislaby@kernel.org,
	songmuchun@bytedance.com, qydwhotmail@gmail.com,
	hughd@google.com, ziy@nvidia.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v3 2/4] mm/page_table_check: use unsigned long for page counters and cleanup
Date: Tue, 25 Jan 2022 22:29:45 -0800 (PST)	[thread overview]
Message-ID: <3554d255-dc76-c4a1-e2a1-f110f1e2c7b5@google.com> (raw)
In-Reply-To: <20220126060514.1574935-3-pasha.tatashin@soleen.com>

On Wed, 26 Jan 2022, Pasha Tatashin wrote:

> For the consistency, use "unsigned long" for all page counters.
> 
> Also, reduce code duplication by calling
> __page_table_check_*_clear() from __page_table_check_*_set() functions.
> 
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> Reviewed-by: Wei Xu <weixugc@google.com>

Acked-by: David Rientjes <rientjes@google.com>

  reply	other threads:[~2022-01-26  6:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  6:05 [PATCH v3 0/4] page table check fixes and cleanups Pasha Tatashin
2022-01-26  6:05 ` [PATCH v3 1/4] mm/debug_vm_pgtable: remove pte entry from the page table Pasha Tatashin
2022-01-26  6:26   ` David Rientjes
2022-01-26  6:05 ` [PATCH v3 2/4] mm/page_table_check: use unsigned long for page counters and cleanup Pasha Tatashin
2022-01-26  6:29   ` David Rientjes [this message]
2022-01-26  6:05 ` [PATCH v3 3/4] mm/khugepaged: unify collapse pmd clear, flush and free Pasha Tatashin
2022-01-26  6:34   ` David Rientjes
2022-01-26 12:34     ` Pasha Tatashin
2022-01-26  6:05 ` [PATCH v3 4/4] mm/page_table_check: check entries at pmd levels Pasha Tatashin
2022-01-26  6:45   ` David Rientjes
2022-01-26 12:46     ` 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=3554d255-dc76-c4a1-e2a1-f110f1e2c7b5@google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gthelen@google.com \
    --cc=hpa@zytor.com \
    --cc=hughd@google.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pjt@google.com \
    --cc=qydwhotmail@gmail.com \
    --cc=rppt@kernel.org \
    --cc=songmuchun@bytedance.com \
    --cc=weixugc@google.com \
    --cc=will@kernel.org \
    --cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).