From: Sumanth Korikkar <sumanthk@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, linux-mm <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Sumanth Korikkar <sumanthk@linux.ibm.com>
Subject: [RFC PATCH 2/4] mm/memory_hotplug: Add memory block altmap sysfs attribute
Date: Mon, 2 Dec 2024 09:27:30 +0100 [thread overview]
Message-ID: <20241202082732.3959803-3-sumanthk@linux.ibm.com> (raw)
In-Reply-To: <20241202082732.3959803-1-sumanthk@linux.ibm.com>
Currently memmap_on_memory sysfs attribute can determine if the altmap
is supported in the entire system.
However, with CONFIG_RUNTIME_MEMORY_CONFIGURATION, user can dynamically
add or remove individual memory blocks with/without altmap support.
Hence, it is more beneficial to the user, if the altmap support can also
be represented per memory block.
lsmem output could look like the following:
RANGE SIZE STATE BLOCK ALTMAP
0x0000000000000000-0x000000007fffffff 2G online 0-7 0
0x0000000080000000-0x00000001ffffffff 6G online 8-31 0
0x0000000200000000-0x00000002ffffffff 4G offline 32-47 1
Reviewed-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Signed-off-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
---
drivers/base/memory.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index f024444b3301..469adc7212fc 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -431,6 +431,14 @@ static ssize_t phys_device_show(struct device *dev,
arch_get_memory_phys_device(start_pfn));
}
+static ssize_t altmap_show(struct device *dev,
+ struct device_attribute *attr, char *buf)
+{
+ struct memory_block *mem = to_memory_block(dev);
+
+ return sysfs_emit(buf, "%u\n", mem->altmap ? 1 : 0);
+}
+
#ifdef CONFIG_MEMORY_HOTREMOVE
static int print_allowed_zone(char *buf, int len, int nid,
struct memory_group *group,
@@ -492,6 +500,7 @@ static DEVICE_ATTR_RO(phys_index);
static DEVICE_ATTR_RW(state);
static DEVICE_ATTR_RO(phys_device);
static DEVICE_ATTR_RO(removable);
+static DEVICE_ATTR_RO(altmap);
/*
* Show the memory block size (shared by all memory blocks).
@@ -785,6 +794,7 @@ static struct attribute *memory_memblk_attrs[] = {
#ifdef CONFIG_MEMORY_HOTREMOVE
&dev_attr_valid_zones.attr,
#endif
+ &dev_attr_altmap.attr,
NULL
};
--
2.45.2
next prev parent reply other threads:[~2024-12-05 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 8:27 [RFC PATCH 0/4] Support dynamic (de)configuration of memory Sumanth Korikkar
2024-12-02 8:27 ` [RFC PATCH 1/4] mm/memory_hotplug: Add interface for runtime " Sumanth Korikkar
2024-12-02 16:55 ` David Hildenbrand
2024-12-03 14:33 ` Sumanth Korikkar
2024-12-20 15:53 ` David Hildenbrand
2025-05-20 13:06 ` Sumanth Korikkar
2025-05-20 17:55 ` David Hildenbrand
2025-05-21 10:34 ` Sumanth Korikkar
2025-05-21 12:33 ` David Hildenbrand
2025-05-21 14:21 ` Heiko Carstens
2025-05-21 14:25 ` David Hildenbrand
2025-05-21 14:24 ` Sumanth Korikkar
2024-12-02 8:27 ` Sumanth Korikkar [this message]
2024-12-02 8:27 ` [RFC PATCH 3/4] mm/memory_hotplug: Add max_configurable sysfs read attribute Sumanth Korikkar
2024-12-02 8:27 ` [RFC PATCH 4/4] s390/sclp: Add support for dynamic (de)configuration of memory Sumanth Korikkar
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=20241202082732.3959803-3-sumanthk@linux.ibm.com \
--to=sumanthk@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.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=osalvador@suse.de \
/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