linux-kernel - Re: [PATCH] Make CONFIG_MIGRATION available for s390

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 5 Jul 2008 13:02:03 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Gerald Schaefer <gerald.schaefer@...ibm.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
	Yasunori Goto <y-goto@...fujitsu.com>,
	Dave Hansen <haveblue@...ibm.com>,
	Andy Whitcroft <apw@...dowen.org>
Subject: Re: [PATCH] Make CONFIG_MIGRATION available for s390

On Fri, 04 Jul 2008 16:58:59 +0200
Gerald Schaefer <gerald.schaefer@...ibm.com> wrote:

> Subject: [PATCH] Make CONFIG_MIGRATION available for s390
> 
> From: Gerald Schaefer <gerald.schaefer@...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@...ibm.com>
> ---

Maybe make sense

Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.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 from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/