From: Oscar Salvador <osalvador@suse.de>
To: glaubitz@physik.fu-berlin.de
Cc: geert+renesas@glider.be, david@redhat.com, linux-sh@vger.kernel.org
Subject: drop memory-hotplug on superH
Date: Thu, 16 May 2024 22:25:28 +0200 [thread overview]
Message-ID: <ZkZruHmlKd7GaRHs@localhost.localdomain> (raw)
Hi,
After talking to Adrian Glaubitz about superH and memory-hotplug, he mentioned
that currently superH runs only on 32bits (there was a 64bit version but no is
longer supported?).
The thing is that since the below commit
commit 7ec58a2b941ed88986694d037e38012738323171
Author: David Hildenbrand <david@redhat.com>
Date: Fri Nov 5 13:44:28 2021 -0700
mm/memory_hotplug: restrict CONFIG_MEMORY_HOTPLUG to 64 bit
we no longer support memory-hotplug on 32bit platforms, so let us drop the
memory-hotplug code for superH because it is a no-op at the moment.
If there is ever a 64bit platform again, we shall re-implement it, and we
shall do it on CONFIG_SPARSEMEM_VMEMMAP, since we plan do make memory-hotplug
dependant on that, and drop support for CONFIG_SPARSEMEM &&
!CONFIG_SPARSEMEM_VMEMMAP environments.
I prepared two patches at [1] that drop the code and the CONFIG_MEMORY_HOTPLUG_foo
from the Kconfigs.
Let me know if you are fine with that and I shall send it.
Thanks
[1] https://github.com/leberus/linux/tree/deprecate-memhotplug-sh
--
Oscar Salvador
SUSE Labs
next reply other threads:[~2024-05-16 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 20:25 Oscar Salvador [this message]
2024-05-16 20:30 ` drop memory-hotplug on superH David Hildenbrand
2024-05-17 1:11 ` D. Jeff Dionne
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=ZkZruHmlKd7GaRHs@localhost.localdomain \
--to=osalvador@suse.de \
--cc=david@redhat.com \
--cc=geert+renesas@glider.be \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-sh@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).