mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Reale <ar@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, zi.yan@cs.rutgers.edu,
	n-horiguchi@ah.jp.nec.com
Cc: akpm@linux-foundation.org, jglisse@redhat.com, realean2@ie.ibm.com
Subject: [PATCH 1/1] mm/migrate: do not call prep_transhuge_page if !thp_migration_supported
Date: Mon, 20 Nov 2017 16:17:56 +0000	[thread overview]
Message-ID: <2eebd2959214f4dc2b2e9fa7f1059208c6650e8c.1511193197.git.ar@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1511193197.git.ar@linux.vnet.ibm.com>

new_page_nodemask in linux/migrate.h should not call prep_transhuge_page
if thp_migration_support is false.

Fixes commit 8135d8926c08 ("mm: memory_hotplug: memory hotremove supports
thp migration")

Signed-off-by: Andrea Reale <ar@linux.vnet.ibm.com>
---
 include/linux/migrate.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/migrate.h b/include/linux/migrate.h
index 895ec0c..725eac5 100644
--- a/include/linux/migrate.h
+++ b/include/linux/migrate.h
@@ -54,7 +54,7 @@ static inline struct page *new_page_nodemask(struct page *page,
 	new_page = __alloc_pages_nodemask(gfp_mask, order,
 				preferred_nid, nodemask);
 
-	if (new_page && PageTransHuge(page))
+	if (thp_migration_supported() && new_page && PageTransHuge(page))
 		prep_transhuge_page(new_page);
 
 	return new_page;
-- 
2.7.4

  reply	other threads:[~2017-11-20 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 16:17 [PATCH 0/1] " Andrea Reale
2017-11-20 16:17 ` Andrea Reale [this message]
2017-11-20 16:33   ` [PATCH 1/1] " Zi Yan
2017-11-20 17:07     ` Andrea Reale

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=2eebd2959214f4dc2b2e9fa7f1059208c6650e8c.1511193197.git.ar@linux.vnet.ibm.com \
    --to=ar@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=realean2@ie.ibm.com \
    --cc=zi.yan@cs.rutgers.edu \
    /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

all inboxes | Powered by JetHome®