linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 0/3] mm/memory_hotplug: fixes for memory hotplug altmap support
@ 2023-11-20 10:27 Sumanth Korikkar
  2023-11-20 10:27 ` [PATCH v2 2/3] mm/memory_hotplug: fix error handling in add_memory_resource() Sumanth Korikkar
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Sumanth Korikkar @ 2023-11-20 10:27 UTC (permalink / raw)
  To: linux-mm, Andrew Morton, David Hildenbrand
  Cc: Oscar Salvador, Michal Hocko, Aneesh Kumar K.V,
	Anshuman Khandual, Gerald Schaefer, Alexander Gordeev,
	Heiko Carstens, Vasily Gorbik, linux-s390, LKML, stable

Patch 1  adds  the missing lock  in memory hotplug operations,
ensuring that the mem_hotplug_lock is held during critical operations
like mhp_init_memmap_on_memory() and mhp_deinit_memmap_on_memory()

Patch 2 deals with error handling in add_memory_resource() and considers
the possibility of altmap support. This ensures proper deallocation of
struct pages, aligning with the allocation strategy.

Patch 3 relocates the vmem_altmap code to sparse-vmemmap.c, enabling the
utilization of vmem_altmap_free() and vmem_altmap_offset() without the
dependency on CONFIG_ZONE_DEVICE.

v2:
* cc: stable@vger.kernel.org
* made vmem_altmap_offset()/vmem_altmap_free() inline.
* added Acked-by for patch 1 and patch 2.

v1:
Changes since patch series "implement "memmap on memory" feature on
s390:
Patch 1 (Feedback from David):
* Fixed subject for memory hotplug lock.
* Added locking comments before
  memory_block_online()/memory_block_offline().
Patch 2 (Feedback from David):
* Fixed Fixes-by commit.
Patch 3 (lkp report):
* when CONFIG_SPARSEMEM_VMEMMAP is disabled, resolve
  undefined reference to `vmem_altmap_offset' error.
* Request for Reviewed-by once again due to the change in patch3.

Thank you

Sumanth Korikkar (3):
  mm/memory_hotplug: add missing mem_hotplug_lock
  mm/memory_hotplug: fix error handling in add_memory_resource()
  mm: use vmem_altmap code without CONFIG_ZONE_DEVICE

 drivers/base/memory.c    | 18 +++++++++++++++---
 include/linux/memremap.h | 12 ------------
 include/linux/mm.h       | 26 ++++++++++++++++++++++++++
 mm/memory_hotplug.c      | 15 +++++++--------
 mm/memremap.c            | 14 +-------------
 5 files changed, 49 insertions(+), 36 deletions(-)

-- 
2.41.0



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-11-20 10:55 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-20 10:27 [PATCH v2 0/3] mm/memory_hotplug: fixes for memory hotplug altmap support Sumanth Korikkar
2023-11-20 10:27 ` [PATCH v2 2/3] mm/memory_hotplug: fix error handling in add_memory_resource() Sumanth Korikkar
     [not found] ` <20231120102734.2001576-2-sumanthk@linux.ibm.com>
2023-11-20 10:53   ` [PATCH v2 1/3] mm/memory_hotplug: add missing mem_hotplug_lock Greg KH
     [not found] ` <20231120102734.2001576-4-sumanthk@linux.ibm.com>
2023-11-20 10:55   ` [PATCH v2 3/3] mm: use vmem_altmap code without CONFIG_ZONE_DEVICE David Hildenbrand

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox