From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, huntbag@linux.vnet.ibm.com,
dave.hansen@linux.intel.com, baolin.wang@linux.alibaba.com,
osalvador@suse.de, akpm@linux-foundation.org
Subject: [folded-merged] mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state-v3.patch removed from -mm tree
Date: Tue, 22 Mar 2022 12:16:12 -0700 [thread overview]
Message-ID: <20220322191613.085F2C340EC@smtp.kernel.org> (raw)
The patch titled
Subject: mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state-v3
has been removed from the -mm tree. Its filename was
mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state-v3.patch
This patch was dropped because it was folded into mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state.patch
------------------------------------------------------
From: Oscar Salvador <osalvador@suse.de>
Subject: mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state-v3
add feedback from Huang Ying
Link: https://lkml.kernel.org/r/20220314150945.12694-1-osalvador@suse.de
Fixes: 884a6e5d1f93b ("mm/migrate: update node demotion order on hotplug events")
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Tested-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Reported-by: Abhishek Goel <huntbag@linux.vnet.ibm.com>
Signed-off-by: Oscar Salvador <osalvador@suse.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/migrate.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--- a/mm/migrate.c~mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state-v3
+++ a/mm/migrate.c
@@ -3280,12 +3280,16 @@ void __init migrate_on_reclaim_init(void
GFP_KERNEL);
WARN_ON(!node_demotion);
+ hotplug_memory_notifier(migrate_on_reclaim_callback, 100);
/*
* At this point, all numa nodes with memory/CPus have their state
* properly set, so we can build the demotion order now.
+ * Let us hold the cpu_hotplug lock just, as we could possibily have
+ * CPU hotplug events during boot.
*/
+ cpus_read_lock();
set_migration_target_nodes();
- hotplug_memory_notifier(migrate_on_reclaim_callback, 100);
+ cpus_read_unlock();
}
#endif /* CONFIG_HOTPLUG_CPU */
_
Patches currently in -mm which might be from osalvador@suse.de are
arch-x86-mm-numa-do-not-initialize-nodes-twice.patch
mm-only-re-generate-demotion-targets-when-a-numa-node-changes-its-n_cpu-state.patch
reply other threads:[~2022-03-22 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220322191613.085F2C340EC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=osalvador@suse.de \
/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.