linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Weizhao Ouyang <o451686892@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Anshuman Khandual <khandual@linux.vnet.ibm.com>,
	Michal Hocko <mhocko@suse.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Yang Shi <yang.shi@linux.alibaba.com>, Zi Yan <ziy@nvidia.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Minchan Kim <minchan@kernel.org>,
	Mina Almasry <almasrymina@google.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	"Huang, Ying" <ying.huang@intel.com>,
	Oscar Salvador <osalvador@suse.de>, Wei Xu <weixugc@google.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/debug: sync up MR_CONTIG_RANGE and MR_LONGTERM_PIN
Date: Tue, 21 Sep 2021 21:48:38 -0700	[thread overview]
Message-ID: <fb44af69-6353-e18d-af0e-fd154cef14e8@nvidia.com> (raw)
In-Reply-To: <20210921064553.293905-2-o451686892@gmail.com>

On 9/20/21 23:45, Weizhao Ouyang wrote:
> Sync up MR_CONTIG_RANGE and MR_LONGTERM_PIN to migrate_reason_names.
> 
> Fixes: 310253514bbf ("mm/migrate: rename migration reason MR_CMA to MR_CONTIG_RANGE")
> Fixes: d1e153fea2a8 ("mm/gup: migrate pinned pages out of movable zone")
> Cc: stable@vger.kernel.org
> Signed-off-by: Weizhao Ouyang <o451686892@gmail.com>
> Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
> ---
>   mm/debug.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/debug.c b/mm/debug.c
> index e73fe0a8ec3d..e61037cded98 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -24,7 +24,8 @@ const char *migrate_reason_names[MR_TYPES] = {
>   	"syscall_or_cpuset",
>   	"mempolicy_mbind",
>   	"numa_misplaced",
> -	"cma",
> +	"contig_range",
> +	"longterm_pin",
>   };
>   
>   const struct trace_print_flags pageflag_names[] = {
> 

Looks good.

Reviewed-by: John Hubbard <jhubbard@nvidia.com>


thanks,
-- 
John Hubbard
NVIDIA


      parent reply	other threads:[~2021-09-22  4:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210921064553.293905-1-o451686892@gmail.com>
2021-09-21  6:45 ` [PATCH v2 2/2] mm/debug: sync up latest migrate_reason to migrate_reason_names Weizhao Ouyang
2021-09-21  7:07   ` Huang, Ying
2021-09-21  7:31     ` Weizhao Ouyang
2021-09-21 14:06       ` Huang, Ying
2021-09-21 18:00         ` John Hubbard
2021-09-21 21:53           ` John Hubbard
2021-09-22  2:07           ` Huang, Ying
2021-09-22  4:49   ` John Hubbard
     [not found] ` <20210921064553.293905-2-o451686892@gmail.com>
2021-09-22  4:48   ` John Hubbard [this message]

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=fb44af69-6353-e18d-af0e-fd154cef14e8@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=almasrymina@google.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=o451686892@gmail.com \
    --cc=osalvador@suse.de \
    --cc=pasha.tatashin@soleen.com \
    --cc=stable@vger.kernel.org \
    --cc=weixugc@google.com \
    --cc=willy@infradead.org \
    --cc=yang.shi@linux.alibaba.com \
    --cc=ying.huang@intel.com \
    --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