From: David Hildenbrand <david@redhat.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Sumanth Korikkar <sumanthk@linux.ibm.com>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH v2 0/4] Support dynamic (de)configuration of memory
Date: Fri, 10 Oct 2025 11:02:36 +0200 [thread overview]
Message-ID: <1be7d08f-7de4-4f7d-8897-ef90d2188d5a@redhat.com> (raw)
In-Reply-To: <20251010082422.9132Ab1-hca@linux.ibm.com>
On 10.10.25 10:24, Heiko Carstens wrote:
> On Thu, Oct 09, 2025 at 03:18:35PM +0200, Sumanth Korikkar wrote:
>> Hi,
>>
>> Patchset provides a new interface for dynamic configuration and
>> deconfiguration of hotplug memory on s390, allowing with/without
>> memmap_on_memory support. It is a follow up on the discussion with David
>> when introducing memmap_on_memory support for s390 and support dynamic
>> (de)configuration of memory:
>> https://lore.kernel.org/all/ee492da8-74b4-4a97-8b24-73e07257f01d@redhat.com/
>> https://lore.kernel.org/all/20241202082732.3959803-1-sumanthk@linux.ibm.com/
>
> Andrew, David, we would like to carry this series via the s390 tree,
> including the fourth patch, which is common code only.
>
> Is this ok for both of you?
Fine with me, I don't expect a lot of memory hotplug changes that could
interact.
As an alternative, we could route #4 separately later through mm.
But this one feels like it can just all go through the mm tree if Andrew
is fine with it.
--
Cheers
David / dhildenb
prev parent reply other threads:[~2025-10-10 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 13:18 Sumanth Korikkar
2025-10-09 13:18 ` [PATCH v2 1/4] s390/mm: Support removal of boot-allocated virtual memory map Sumanth Korikkar
2025-10-09 13:18 ` [PATCH v2 2/4] s390/sclp: Add support for dynamic (de)configuration of memory Sumanth Korikkar
2025-10-09 19:13 ` David Hildenbrand
2025-10-10 8:09 ` Sumanth Korikkar
2025-10-10 8:16 ` David Hildenbrand
2025-10-09 13:18 ` [PATCH v2 3/4] s390/sclp: Remove MHP_OFFLINE_INACCESSIBLE Sumanth Korikkar
2025-10-09 13:18 ` [PATCH v2 4/4] mm/memory_hotplug: Remove MEM_PREPARE_ONLINE/MEM_FINISH_OFFLINE notifiers Sumanth Korikkar
2025-10-09 19:03 ` David Hildenbrand
2025-10-10 8:24 ` [PATCH v2 0/4] Support dynamic (de)configuration of memory Heiko Carstens
2025-10-10 9:02 ` David Hildenbrand [this message]
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=1be7d08f-7de4-4f7d-8897-ef90d2188d5a@redhat.com \
--to=david@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--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=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