From: Liu Shixin <liushixin2@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>,
Christoph Lameter <cl@linux.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Liu Shixin <liushixin2@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v3 0/8] mm: Use hotplug_memory_notifier() instead of register_hotmemory_notifier()
Date: Thu, 22 Sep 2022 22:18:56 +0800 [thread overview]
Message-ID: <20220922141904.3245505-1-liushixin2@huawei.com> (raw)
Patch f02c69680088 introduced register_hotmemory_notifier() to avoid a
compile problem with gcc-4.4.4:
When CONFIG_MEMORY_HOTPLUG=n, we don't want the memory-hotplug notifier
handlers to be included in the .o files, for space reasons.
The existing hotplug_memory_notifier() tries to handle this but testing
with gcc-4.4.4 shows that it doesn't work - the hotplug functions are
still present in the .o files.
Since patch 316346243be6 has already updated the minimum gcc version to 5.1.
The previous problem mentioned in patch f02c69680088 is not existed. So we
can now revert to use hotplug_memory_notifier() directly rather than
register_hotmemory_notifier().
In the last patch, we move all hotplug memory notifier priority to same
file for easy sorting.
Patch [1-6] replace register_hotmemory_notifier() with hotplug_memory_notifier()
for every caller.
Patch [7] remove unused register_hotmemory_notifier().
Patch [9] move all priority of hotplug memory callback into include/linux/memory.h
for easy sorting.
v2->v3: fold last two patches, change MM_BATCH_CALLBACK_PRI to
MM_COMPUTE_BATCH_PRI and rewrite the commit log.
v1->v2: fix compile error of patch [4,5].
Liu Shixin (8):
cgroup/cpuset: use hotplug_memory_notifier() directly
fs/proc/kcore.c: use hotplug_memory_notifier() directly
mm/slub.c: use hotplug_memory_notifier() directly
mm/mmap: use hotplug_memory_notifier() directly
mm/mm_init.c: use hotplug_memory_notifier() directly
ACPI: HMAT: use hotplug_memory_notifier() directly
memory: remove unused register_hotmemory_notifier()
memory: move hotplug memory notifier priority to same file for easy
sorting
drivers/acpi/numa/hmat.c | 7 +------
fs/proc/kcore.c | 7 +------
include/linux/memory-tiers.h | 1 -
include/linux/memory.h | 15 +++++++--------
kernel/cgroup/cpuset.c | 7 +------
mm/kasan/shadow.c | 2 +-
mm/ksm.c | 2 +-
mm/memory-tiers.c | 2 +-
mm/mm_init.c | 8 +-------
mm/mmap.c | 6 +-----
mm/page_ext.c | 2 +-
mm/slub.c | 7 +------
12 files changed, 17 insertions(+), 49 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-22 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:18 Liu Shixin [this message]
2022-09-22 14:18 ` [PATCH v3 1/8] cgroup/cpuset: use hotplug_memory_notifier() directly Liu Shixin
2022-09-22 17:56 ` David Hildenbrand
2022-09-23 1:56 ` Liu Shixin
2022-09-22 14:18 ` [PATCH v3 2/8] fs/proc/kcore.c: " Liu Shixin
2022-09-22 14:18 ` [PATCH v3 3/8] mm/slub.c: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 4/8] mm/mmap: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 5/8] mm/mm_init.c: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 6/8] ACPI: HMAT: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 7/8] memory: remove unused register_hotmemory_notifier() Liu Shixin
2022-09-22 14:19 ` [PATCH v3 8/8] memory: move hotplug memory notifier priority to same file for easy sorting Liu Shixin
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=20220922141904.3245505-1-liushixin2@huawei.com \
--to=liushixin2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=wangkefeng.wang@huawei.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