From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
andi@firstfloor.org, akpm@linux-foundation.org,
linux-mm@kvack.org, kamezawa.hiroyuki@gmail.com, mhocko@suse.cz,
hannes@cmpxchg.org, yinghan@google.com, jasowang@redhat.com,
kay@vrfy.org
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks
Date: Fri, 19 Jul 2013 12:23:05 -0700 [thread overview]
Message-ID: <1374261785-1615-1-git-send-email-kys@microsoft.com> (raw)
The current machinery for hot-adding memory requires having udev
rules to bring the memory segments online. Export the necessary functionality
to to bring the memory segment online without involving user space code.
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
---
drivers/base/memory.c | 5 ++++-
include/linux/memory.h | 4 ++++
2 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 2b7813e..a8204ac 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -328,7 +328,7 @@ static int __memory_block_change_state_uevent(struct memory_block *mem,
return ret;
}
-static int memory_block_change_state(struct memory_block *mem,
+int memory_block_change_state(struct memory_block *mem,
unsigned long to_state, unsigned long from_state_req,
int online_type)
{
@@ -341,6 +341,8 @@ static int memory_block_change_state(struct memory_block *mem,
return ret;
}
+EXPORT_SYMBOL(memory_block_change_state);
+
static ssize_t
store_mem_state(struct device *dev,
struct device_attribute *attr, const char *buf, size_t count)
@@ -540,6 +542,7 @@ struct memory_block *find_memory_block(struct mem_section *section)
{
return find_memory_block_hinted(section, NULL);
}
+EXPORT_SYMBOL(find_memory_block);
static struct attribute *memory_memblk_attrs[] = {
&dev_attr_phys_index.attr,
diff --git a/include/linux/memory.h b/include/linux/memory.h
index 85c31a8..8e3ede5 100644
--- a/include/linux/memory.h
+++ b/include/linux/memory.h
@@ -115,6 +115,10 @@ extern void unregister_memory_notifier(struct notifier_block *nb);
extern int register_memory_isolate_notifier(struct notifier_block *nb);
extern void unregister_memory_isolate_notifier(struct notifier_block *nb);
extern int register_new_memory(int, struct mem_section *);
+extern int memory_block_change_state(struct memory_block *mem,
+ unsigned long to_state, unsigned long from_state_req,
+ int online_type);
+
#ifdef CONFIG_MEMORY_HOTREMOVE
extern int unregister_memory_section(struct mem_section *);
#endif
--
1.7.4.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2013-07-19 18:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 19:23 K. Y. Srinivasan [this message]
2013-07-22 3:16 ` [PATCH 1/1] Drivers: base: memory: Export symbols for onlining memory blocks Jason Wang
2013-07-22 12:37 ` Michal Hocko
2013-07-23 14:52 ` KY Srinivasan
2013-07-23 15:09 ` Michal Hocko
2013-07-23 15:50 ` KY Srinivasan
2013-07-23 15:28 ` Dave Hansen
2013-07-23 15:54 ` KY Srinivasan
2013-07-23 16:00 ` Dave Hansen
2013-07-23 17:21 ` KY Srinivasan
2013-07-24 16:43 ` Dave Hansen
2013-07-24 19:45 ` KY Srinivasan
2013-07-24 21:02 ` Dave Hansen
2013-07-25 7:57 ` Michal Hocko
2013-07-25 11:14 ` KY Srinivasan
2013-07-25 15:03 ` Dave Hansen
2013-07-25 15:15 ` Kay Sievers
2013-07-25 16:35 ` Dave Hansen
2013-07-25 15:49 ` KY Srinivasan
2013-07-23 16:01 ` Greg KH
2013-07-23 16:54 ` KY Srinivasan
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=1374261785-1615-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=jasowang@redhat.com \
--cc=kamezawa.hiroyuki@gmail.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=olaf@aepfle.de \
--cc=yinghan@google.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;
as well as URLs for NNTP newsgroup(s).