All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: travis@sgi.com
Cc: Andi Kleen <ak@suse.de>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1/6] x86: fix cpu_to_node references (v2)
Date: Fri, 24 Aug 2007 17:23:49 -0700	[thread overview]
Message-ID: <20070825002349.GB1894@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070824222948.587159000@sgi.com>

On Fri, Aug 24, 2007 at 03:26:55PM -0700, travis@sgi.com wrote:
> Fix four instances where cpu_to_node is referenced
> by array instead of via the cpu_to_node macro.  This
> is preparation to moving it to the per_cpu data area.
> 
...

>  unsigned long __init numa_free_all_bootmem(void) 
> --- a/arch/x86_64/mm/srat.c
> +++ b/arch/x86_64/mm/srat.c
> @@ -431,9 +431,9 @@
>  			setup_node_bootmem(i, nodes[i].start, nodes[i].end);
>  
>  	for (i = 0; i < NR_CPUS; i++) {
> -		if (cpu_to_node[i] == NUMA_NO_NODE)
> +		if (cpu_to_node(i) == NUMA_NO_NODE)
>  			continue;
> -		if (!node_isset(cpu_to_node[i], node_possible_map))
> +		if (!node_isset(cpu_to_node(i), node_possible_map))
>  			numa_set_node(i, NUMA_NO_NODE);
>  	}
>  	numa_init_array();

During this particular routine execution, per cpu areas are not yet setup. In
future, when we make cpu_to_node(i) use per cpu area, then this code will break.

And actually setup_per_cpu_areas() uses cpu_to_node(). So...

thanks,
suresh

WARNING: multiple messages have this Message-ID (diff)
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: travis@sgi.com
Cc: Andi Kleen <ak@suse.de>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1/6] x86: fix cpu_to_node references (v2)
Date: Fri, 24 Aug 2007 17:23:49 -0700	[thread overview]
Message-ID: <20070825002349.GB1894@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070824222948.587159000@sgi.com>

On Fri, Aug 24, 2007 at 03:26:55PM -0700, travis@sgi.com wrote:
> Fix four instances where cpu_to_node is referenced
> by array instead of via the cpu_to_node macro.  This
> is preparation to moving it to the per_cpu data area.
> 
...

>  unsigned long __init numa_free_all_bootmem(void) 
> --- a/arch/x86_64/mm/srat.c
> +++ b/arch/x86_64/mm/srat.c
> @@ -431,9 +431,9 @@
>  			setup_node_bootmem(i, nodes[i].start, nodes[i].end);
>  
>  	for (i = 0; i < NR_CPUS; i++) {
> -		if (cpu_to_node[i] == NUMA_NO_NODE)
> +		if (cpu_to_node(i) == NUMA_NO_NODE)
>  			continue;
> -		if (!node_isset(cpu_to_node[i], node_possible_map))
> +		if (!node_isset(cpu_to_node(i), node_possible_map))
>  			numa_set_node(i, NUMA_NO_NODE);
>  	}
>  	numa_init_array();

During this particular routine execution, per cpu areas are not yet setup. In
future, when we make cpu_to_node(i) use per cpu area, then this code will break.

And actually setup_per_cpu_areas() uses cpu_to_node(). So...

thanks,
suresh

--
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>

  reply	other threads:[~2007-08-25  0:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 22:26 [PATCH 0/6] x86: Reduce Memory Usage and Inter-Node message traffic (v2) travis
2007-08-24 22:26 ` travis
2007-08-24 22:26 ` [PATCH 1/6] x86: fix cpu_to_node references (v2) travis
2007-08-24 22:26   ` travis
2007-08-25  0:23   ` Siddha, Suresh B [this message]
2007-08-25  0:23     ` Siddha, Suresh B
2007-08-27 19:47     ` Mike Travis
2007-08-27 19:47       ` Mike Travis
2007-08-24 22:26 ` [PATCH 2/6] x86: Convert cpu_core_map to be a per cpu variable (v2) travis
2007-08-24 22:26   ` travis
2007-08-24 22:26 ` [PATCH 3/6] x86: Convert cpu_sibling_map " travis
2007-08-24 22:26   ` travis
2007-09-01  2:49   ` Andrew Morton
2007-09-01  2:49     ` Andrew Morton
2007-09-01 11:34     ` Kamalesh Babulal
2007-09-01 11:34       ` Kamalesh Babulal
2007-09-01 16:10       ` Andrew Morton
2007-09-01 16:10         ` Andrew Morton
2007-09-02 11:48         ` Kamalesh Babulal
2007-09-02 11:48           ` Kamalesh Babulal
2007-09-01 14:06     ` Andi Kleen
2007-09-01 14:06       ` Andi Kleen
2007-08-24 22:26 ` [PATCH 4/6] x86: Convert x86_cpu_to_apicid " travis
2007-08-24 22:26   ` travis
2007-08-24 22:26 ` [PATCH 5/6] x86: Convert cpu_llc_id " travis
2007-08-24 22:26   ` travis
2007-08-24 22:27 ` [PATCH 6/6] x86: acpi-use-cpu_physical_id (v2) travis
2007-08-24 22:27   ` travis
2007-08-25  0:50 ` [PATCH 0/6] x86: Reduce Memory Usage and Inter-Node message traffic (v2) Siddha, Suresh B
2007-08-25  0:50   ` Siddha, Suresh B
2007-08-25  9:24   ` Andi Kleen
2007-08-25  9:24     ` Andi Kleen
2007-08-25 16:52     ` Randy Dunlap
2007-08-25 16:52       ` Randy Dunlap
2007-08-27 18:46     ` Mike Travis
2007-08-27 18:46       ` Mike Travis

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=20070825002349.GB1894@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=travis@sgi.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.