From: liangxi Liu <lgs156412@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Fwd: [PATCH v2] memblock: export memblock_free() to free reserved memory.
Date: Tue, 25 Jun 2024 20:08:51 +0800 [thread overview]
Message-ID: <CAPRrSS-Qf_hT2_ZDiyMLG-Jj9ymKcpvvBvzrK-4DgtdS8QAikw@mail.gmail.com> (raw)
In-Reply-To: <20240625115825.1163653-1-lgs156412@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
---------- Forwarded message ---------
From: Guanshun Liu <lgs156412@gmail.com>
Date: Tue, Jun 25, 2024 at 7:58 PM
Subject: [PATCH v2] memblock: export memblock_free() to free reserved
memory.
To: <rppt@kernel.org>
Cc: <akpm@linux-foundation.org>, Guanshun Liu <lgs156412@gmail.com>
On architectures that support the preservation of memblock metadata
after __init, allow drivers to call memblock_free() to free a
reservation configured in dts. This is a hack to support the
freeing of bootsplash reservations passed to Linux by the bootloader.
Signed-off-by: Guanshun Liu <lgs156412@gmail.com>
---
mm/memblock.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/memblock.c b/mm/memblock.c
index 6d18485571b4..20e7f81fc076 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -848,6 +848,9 @@ void __init_memblock memblock_free(void *ptr, size_t
size)
if (ptr)
memblock_phys_free(__pa(ptr), size);
}
+#ifdef CONFIG_ARCH_KEEP_MEMBLOCK
+EXPORT_SYMBOL_GPL(memblock_free);
+#endif
/**
* memblock_phys_free - free boot memory block
--
2.25.1
[-- Attachment #2: Type: text/html, Size: 1688 bytes --]
parent reply other threads:[~2024-06-25 12:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240625115825.1163653-1-lgs156412@gmail.com>]
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=CAPRrSS-Qf_hT2_ZDiyMLG-Jj9ymKcpvvBvzrK-4DgtdS8QAikw@mail.gmail.com \
--to=lgs156412@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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