linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: linux-sh@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Oscar Salvador <osalvador@suse.de>
Subject: [PATCH 1/2] arch/sh: Remove code that handles memory-hotplug and memory-hotremove
Date: Sat, 18 May 2024 13:58:07 +0200	[thread overview]
Message-ID: <20240518115808.8888-2-osalvador@suse.de> (raw)
In-Reply-To: <20240518115808.8888-1-osalvador@suse.de>

Since commit 7ec58a2b941ed889("mm/memory_hotplug: restrict
CONFIG_MEMORY_HOTPLUG to 64 bit"), we only support memory-hotplug on
64bits platforms, but currently superH can only run on 32bit, so
remove the code that handles memory-hotplug and memory-hotremove as
that cannot work.

Signed-off-by: Oscar Salvador <osalvador@suse.de>
---
 arch/sh/mm/init.c | 28 ----------------------------
 1 file changed, 28 deletions(-)

diff --git a/arch/sh/mm/init.c b/arch/sh/mm/init.c
index bf1b54055316..d1fe90b2f5ff 100644
--- a/arch/sh/mm/init.c
+++ b/arch/sh/mm/init.c
@@ -395,31 +395,3 @@ void __init mem_init(void)
 
 	mem_init_done = 1;
 }
-
-#ifdef CONFIG_MEMORY_HOTPLUG
-int arch_add_memory(int nid, u64 start, u64 size,
-		    struct mhp_params *params)
-{
-	unsigned long start_pfn = PFN_DOWN(start);
-	unsigned long nr_pages = size >> PAGE_SHIFT;
-	int ret;
-
-	if (WARN_ON_ONCE(params->pgprot.pgprot != PAGE_KERNEL.pgprot))
-		return -EINVAL;
-
-	/* We only have ZONE_NORMAL, so this is easy.. */
-	ret = __add_pages(nid, start_pfn, nr_pages, params);
-	if (unlikely(ret))
-		printk("%s: Failed, __add_pages() == %d\n", __func__, ret);
-
-	return ret;
-}
-
-void arch_remove_memory(u64 start, u64 size, struct vmem_altmap *altmap)
-{
-	unsigned long start_pfn = PFN_DOWN(start);
-	unsigned long nr_pages = size >> PAGE_SHIFT;
-
-	__remove_pages(start_pfn, nr_pages, altmap);
-}
-#endif /* CONFIG_MEMORY_HOTPLUG */
-- 
2.45.1



  reply	other threads:[~2024-05-18 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 11:58 [PATCH 0/2] Drop support for memory-hotplug and memory-hotremove on superH Oscar Salvador
2024-05-18 11:58 ` Oscar Salvador [this message]
2024-07-11 10:20   ` [PATCH 1/2] arch/sh: Remove code that handles memory-hotplug and memory-hotremove John Paul Adrian Glaubitz
2024-05-18 11:58 ` [PATCH 2/2] arch/sh: Drop support for " Oscar Salvador
2024-07-11 10:20   ` John Paul Adrian Glaubitz

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=20240518115808.8888-2-osalvador@suse.de \
    --to=osalvador@suse.de \
    --cc=david@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-mm@kvack.org \
    --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