From: David Hildenbrand <david@redhat.com>
To: Sumanth Korikkar <sumanthk@linux.ibm.com>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/8] s390/mm: implement MEM_PHYS_ONLINE MEM_PHYS_OFFLINE memory notifiers
Date: Tue, 14 Nov 2023 19:39:40 +0100 [thread overview]
Message-ID: <458da84d-3838-4c5d-abda-1aebba676186@redhat.com> (raw)
In-Reply-To: <20231114180238.1522782-7-sumanthk@linux.ibm.com>
On 14.11.23 19:02, Sumanth Korikkar wrote:
> Implement MEM_PHYS_ONLINE and MEM_PHYS_OFFLINE memory notifiers on s390
>
> Implementation of MEM_PHYS_ONLINE Memory Notifier:
> * Transition the memory block to an accessible/online state using the
> sclp assign command.
> * Execute __add_pages() for the memory block, enabling a self-contained
> memory map range. For boot-time memory, vmemmap mapping is carried out
> through sparse_init().
>
> Implementation of MEM_PHYS_OFFLINE Memory Notifier:
> * Execute __remove_pages() exclusively for the memory block (applicable
> where a self-contained memory map was possible before).
> * Shift the memory block to an inaccessible/offline state using the sclp
> unassign command.
>
> Additional Implementation Considerations:
> * When MHP_MEMMAP_ON_MEMORY is disabled, the system retains the old
> behavior. This means the memory map is allocated from default memory,
> and struct vmemmap pages are populated during the standby memory
> detection phase.
> * With MHP_MEMMAP_ON_MEMORY enabled (allowing self-contained memory
> map), the memory map is allocated using the self-contained memory map
> range. Struct vmemmap pages are populated during the memory hotplug
> phase.
> * If MACHINE_HAS_EDAT1 is unavailable, MHP_MEMMAP_ON_MEMORY is
> automatically disabled. This ensures that vmemmap pagetables do not
> consume additional memory from the default memory allocator.
> * The MEM_GOING_ONLINE notifier has been modified to perform no
> operation, as MEM_PHYS_ONLINE already executes the sclp assign
> command.
> * The MEM_CANCEL_ONLINE notifier now performs no operation, as
> MEM_PHYS_OFFLINE already executes the sclp unassign command.
> * The call to __add_pages() in arch_add_memory() with altmap support is
> skipped. This operation is deferred and will be performed later in the
> MEM_PHYS_ONLINE notifier.
>
> Reviewed-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
> Signed-off-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
> ---
> arch/s390/mm/init.c | 16 +++++++++++++++-
> drivers/s390/char/sclp_cmd.c | 33 ++++++++++++++++++++++++++++++---
> 2 files changed, 45 insertions(+), 4 deletions(-)
>
> diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c
> index 8d9a60ccb777..db505ed590b2 100644
> --- a/arch/s390/mm/init.c
> +++ b/arch/s390/mm/init.c
> @@ -288,6 +288,12 @@ int arch_add_memory(int nid, u64 start, u64 size,
> rc = vmem_add_mapping(start, size);
> if (rc)
> return rc;
> + /*
> + * If MHP_MEMMAP_ON_MEMORY is enabled, perform __add_pages() during memory
> + * onlining phase
> + */
> + if (params->altmap)
> + return 0;
So we'd have added memory blocks without a memmap? Sorry, but this seems
to further hack into the s390x direction.
Maybe s390x should just provide a dedicate interface to add these memory
blocks instead of adding them during boot and then relying on the old
way of using online/offline set them online/offline.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-11-14 18:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 18:02 [PATCH 0/8] implement "memmap on memory" feature on s390 Sumanth Korikkar
2023-11-14 18:02 ` [PATCH 2/8] mm/memory_hotplug: fix error handling in add_memory_resource() Sumanth Korikkar
2023-11-14 18:36 ` David Hildenbrand
2023-11-15 13:45 ` Sumanth Korikkar
2023-11-14 18:02 ` [PATCH 3/8] mm: use vmem_altmap code without CONFIG_ZONE_DEVICE Sumanth Korikkar
2023-11-16 18:43 ` David Hildenbrand
2023-11-17 21:39 ` kernel test robot
2023-11-14 18:02 ` [PATCH 5/8] s390/mm: allocate vmemmap pages from self-contained memory range Sumanth Korikkar
2023-11-14 18:02 ` [PATCH 7/8] s390/sclp: remove unhandled memory notifier type Sumanth Korikkar
2023-11-16 19:33 ` David Hildenbrand
[not found] ` <20231114180238.1522782-2-sumanthk@linux.ibm.com>
2023-11-14 18:22 ` [PATCH 1/8] mm/memory_hotplug: fix memory hotplug locking order David Hildenbrand
[not found] ` <ZVTKk7J1AcoBBxhR@li-2b55cdcc-350b-11b2-a85c-a78bff51fc11.ibm.com>
2023-11-16 18:40 ` David Hildenbrand
2023-11-17 13:42 ` Sumanth Korikkar
[not found] ` <20231114180238.1522782-5-sumanthk@linux.ibm.com>
2023-11-14 18:27 ` [PATCH 4/8] mm/memory_hotplug: introduce MEM_PHYS_ONLINE/OFFLINE memory notifiers David Hildenbrand
2023-11-15 14:23 ` Sumanth Korikkar
2023-11-16 19:03 ` David Hildenbrand
2023-11-15 15:03 ` Gerald Schaefer
2023-11-16 19:02 ` David Hildenbrand
[not found] ` <20231114180238.1522782-7-sumanthk@linux.ibm.com>
2023-11-14 18:39 ` David Hildenbrand [this message]
2023-11-15 14:20 ` [PATCH 6/8] s390/mm: implement MEM_PHYS_ONLINE MEM_PHYS_OFFLINE " Sumanth Korikkar
2023-11-16 19:16 ` David Hildenbrand
2023-11-16 19:23 ` David Hildenbrand
2023-11-17 13:00 ` Gerald Schaefer
2023-11-20 14:49 ` David Hildenbrand
2023-11-16 23:08 ` [PATCH 0/8] implement "memmap on memory" feature on s390 David Hildenbrand
2023-11-17 13:00 ` Gerald Schaefer
2023-11-17 15:37 ` David Hildenbrand
2023-11-17 19:46 ` Sumanth Korikkar
2023-11-21 13:13 ` Sumanth Korikkar
2023-11-21 13:21 ` Sumanth Korikkar
2023-11-21 14:42 ` David Hildenbrand
2023-11-21 19:24 ` David Hildenbrand
2023-11-22 11:44 ` Sumanth Korikkar
2023-11-17 13:56 ` Sumanth Korikkar
2023-11-17 15:37 ` David Hildenbrand
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=458da84d-3838-4c5d-abda-1aebba676186@redhat.com \
--to=david@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=sumanthk@linux.ibm.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