From: Gerald Schaefer <gerald.schaefer@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Yasunori Goto <y-goto@jp.fujitsu.com>,
Dave Hansen <haveblue@us.ibm.com>,
Andy Whitcroft <apw@shadowen.org>
Subject: [PATCH] Make CONFIG_MIGRATION available for s390
Date: Fri, 04 Jul 2008 16:58:59 +0200 [thread overview]
Message-ID: <1215183539.4834.12.camel@localhost.localdomain> (raw)
Subject: [PATCH] Make CONFIG_MIGRATION available for s390
From: Gerald Schaefer <gerald.schaefer@de.ibm.com>
We'd like to support CONFIG_MEMORY_HOTREMOVE on s390, which depends on
CONFIG_MIGRATION. So far, CONFIG_MIGRATION is only available with NUMA
support.
This patch makes CONFIG_MIGRATION selectable for s390. When MIGRATION
is enabled w/o NUMA, the kernel won't compile because of a missing
"migrate" member in vm_operations_struct and a missing "policy_zone"
definition. To avoid this, those are moved from an "#ifdef CONFIG_NUMA"
section to "#ifdef CONFIG_MIGRATION".
Signed-off-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
---
include/linux/mempolicy.h | 6 ++++--
include/linux/mm.h | 2 ++
mm/Kconfig | 2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
Index: mylinux-git/include/linux/mempolicy.h
===================================================================
--- mylinux-git.orig/include/linux/mempolicy.h
+++ mylinux-git/include/linux/mempolicy.h
@@ -62,6 +62,10 @@ enum {
struct mm_struct;
+#ifdef CONFIG_MIGRATION
+extern enum zone_type policy_zone;
+#endif
+
#ifdef CONFIG_NUMA
/*
@@ -202,8 +206,6 @@ extern struct zonelist *huge_zonelist(st
struct mempolicy **mpol, nodemask_t **nodemask);
extern unsigned slab_node(struct mempolicy *policy);
-extern enum zone_type policy_zone;
-
static inline void check_highest_zone(enum zone_type k)
{
if (k > policy_zone && k != ZONE_MOVABLE)
Index: mylinux-git/include/linux/mm.h
===================================================================
--- mylinux-git.orig/include/linux/mm.h
+++ mylinux-git/include/linux/mm.h
@@ -193,6 +193,8 @@ struct vm_operations_struct {
*/
struct mempolicy *(*get_policy)(struct vm_area_struct *vma,
unsigned long addr);
+#endif
+#ifdef CONFIG_MIGRATION
int (*migrate)(struct vm_area_struct *vma, const nodemask_t *from,
const nodemask_t *to, unsigned long flags);
#endif
Index: mylinux-git/mm/Kconfig
===================================================================
--- mylinux-git.orig/mm/Kconfig
+++ mylinux-git/mm/Kconfig
@@ -174,7 +174,7 @@ config SPLIT_PTLOCK_CPUS
config MIGRATION
bool "Page migration"
def_bool y
- depends on NUMA
+ depends on NUMA || S390
help
Allows the migration of the physical location of pages of processes
while the virtual addresses are not changed. This is useful for
WARNING: multiple messages have this Message-ID (diff)
From: Gerald Schaefer <gerald.schaefer@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Yasunori Goto <y-goto@jp.fujitsu.com>,
Dave Hansen <haveblue@us.ibm.com>,
Andy Whitcroft <apw@shadowen.org>
Subject: [PATCH] Make CONFIG_MIGRATION available for s390
Subject: [PATCH] Make CONFIG_MIGRATION available for s390
Date: Fri, 04 Jul 2008 16:58:59 +0200 [thread overview]
Message-ID: <1215183539.4834.12.camel@localhost.localdomain> (raw)
From: Gerald Schaefer <gerald.schaefer@de.ibm.com>
We'd like to support CONFIG_MEMORY_HOTREMOVE on s390, which depends on
CONFIG_MIGRATION. So far, CONFIG_MIGRATION is only available with NUMA
support.
This patch makes CONFIG_MIGRATION selectable for s390. When MIGRATION
is enabled w/o NUMA, the kernel won't compile because of a missing
"migrate" member in vm_operations_struct and a missing "policy_zone"
definition. To avoid this, those are moved from an "#ifdef CONFIG_NUMA"
section to "#ifdef CONFIG_MIGRATION".
Signed-off-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
---
include/linux/mempolicy.h | 6 ++++--
include/linux/mm.h | 2 ++
mm/Kconfig | 2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
Index: mylinux-git/include/linux/mempolicy.h
===================================================================
--- mylinux-git.orig/include/linux/mempolicy.h
+++ mylinux-git/include/linux/mempolicy.h
@@ -62,6 +62,10 @@ enum {
struct mm_struct;
+#ifdef CONFIG_MIGRATION
+extern enum zone_type policy_zone;
+#endif
+
#ifdef CONFIG_NUMA
/*
@@ -202,8 +206,6 @@ extern struct zonelist *huge_zonelist(st
struct mempolicy **mpol, nodemask_t **nodemask);
extern unsigned slab_node(struct mempolicy *policy);
-extern enum zone_type policy_zone;
-
static inline void check_highest_zone(enum zone_type k)
{
if (k > policy_zone && k != ZONE_MOVABLE)
Index: mylinux-git/include/linux/mm.h
===================================================================
--- mylinux-git.orig/include/linux/mm.h
+++ mylinux-git/include/linux/mm.h
@@ -193,6 +193,8 @@ struct vm_operations_struct {
*/
struct mempolicy *(*get_policy)(struct vm_area_struct *vma,
unsigned long addr);
+#endif
+#ifdef CONFIG_MIGRATION
int (*migrate)(struct vm_area_struct *vma, const nodemask_t *from,
const nodemask_t *to, unsigned long flags);
#endif
Index: mylinux-git/mm/Kconfig
===================================================================
--- mylinux-git.orig/mm/Kconfig
+++ mylinux-git/mm/Kconfig
@@ -174,7 +174,7 @@ config SPLIT_PTLOCK_CPUS
config MIGRATION
bool "Page migration"
def_bool y
- depends on NUMA
+ depends on NUMA || S390
help
Allows the migration of the physical location of pages of processes
while the virtual addresses are not changed. This is useful for
--
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:[~2008-07-04 14:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 14:58 Gerald Schaefer [this message]
2008-07-04 14:58 ` [PATCH] Make CONFIG_MIGRATION available for s390, [PATCH] Make CONFIG_MIGRATION available for s390 Gerald Schaefer
2008-07-05 4:02 ` KAMEZAWA Hiroyuki
2008-07-05 4:02 ` KAMEZAWA Hiroyuki
2008-07-05 6:14 ` Yasunori Goto
2008-07-05 6:14 ` Yasunori Goto
2008-07-06 14:30 ` Gerald Schaefer
2008-07-06 14:30 ` Gerald Schaefer
-- strict thread matches above, loose matches on Subject: below --
2008-07-06 14:35 Gerald Schaefer
2008-07-07 6:22 ` Yasunori Goto
2008-07-07 6:22 ` Yasunori Goto
2008-07-07 9:16 ` Andy Whitcroft
2008-07-07 9:16 ` Andy Whitcroft
2008-07-07 10:24 ` Yasunori Goto
2008-07-07 10:24 ` Yasunori Goto
2008-07-07 16:41 ` Gerald Schaefer
2008-07-07 16:41 ` Gerald Schaefer
2008-07-07 16:53 ` Christoph Lameter
2008-07-07 16:53 ` Christoph Lameter
2008-07-07 15:09 ` Christoph Lameter
2008-07-07 15:09 ` Christoph Lameter
2008-07-07 17:28 ` Gerald Schaefer
2008-07-07 17:28 ` Gerald Schaefer
2008-07-07 17:38 ` Christoph Lameter
2008-07-07 17:38 ` Christoph Lameter
2008-07-07 18:25 ` Gerald Schaefer
2008-07-07 18:25 ` Gerald Schaefer
2008-07-07 18:32 ` Christoph Lameter
2008-07-07 18:32 ` Christoph Lameter
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=1215183539.4834.12.camel@localhost.localdomain \
--to=gerald.schaefer@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schwidefsky@de.ibm.com \
--cc=y-goto@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.