linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mm, numa: boot cpu should bound to the node0 when node_off enable
Date: Thu, 18 Aug 2016 17:04:37 +0100	[thread overview]
Message-ID: <20160818160437.GA21343@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1471525766-12803-1-git-send-email-zhongjiang@huawei.com>

On Thu, Aug 18, 2016 at 09:09:26PM +0800, zhongjiang wrote:
> At present, boot cpu will bound to a node from device tree when node_off enable.
> if the node is not initialization, it will lead to a following problem.
> 
>  next_zones_zonelist+0x18/0x80
>  __build_all_zonelists+0x1e0/0x288
>  build_all_zonelists_init+0x10/0x1c
>  build_all_zonelists+0x114/0x128
>  start_kernel+0x1a0/0x414

I think this "problem" is missing a lot of information. Is this supposed
to be a kernel panic?

> The patch fix it by fallback to node 0. therefore, the cpu will bound to the node
> correctly.
> 
> Signed-off-by: zhongjiang <zhongjiang@huawei.com>
> ---
>  arch/arm64/mm/numa.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c
> index 4dcd7d6..1f8f5da 100644
> --- a/arch/arm64/mm/numa.c
> +++ b/arch/arm64/mm/numa.c
> @@ -119,7 +119,7 @@ void numa_store_cpu_info(unsigned int cpu)
>  void __init early_map_cpu_to_node(unsigned int cpu, int nid)
>  {
>  	/* fallback to node 0 */
> -	if (nid < 0 || nid >= MAX_NUMNODES)
> +	if (nid < 0 || nid >= MAX_NUMNODES || numa_off)
>  		nid = 0;
>  
>  	cpu_to_node_map[cpu] = nid;

The patch looks fine (slight inconsistence from the map_cpu_to_node()
callers but I guess we don't want to expose numa_off outside this file).
I would however like to see an Ack from Ganapat (cc'ed).

-- 
Catalin

  reply	other threads:[~2016-08-18 16:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 13:09 [PATCH] mm, numa: boot cpu should bound to the node0 when node_off enable zhongjiang
2016-08-18 16:04 ` Catalin Marinas [this message]
2016-08-18 17:45   ` Ganapatrao Kulkarni
2016-08-19  1:41     ` zhong jiang
2016-08-19  1:58     ` zhong jiang
2016-08-19  4:00       ` Ganapatrao Kulkarni
2016-08-19  4:11         ` Ganapatrao Kulkarni
2016-08-20  9:38           ` zhong jiang
2016-08-22 14:28             ` Catalin Marinas
2016-08-23  7:47               ` zhong jiang
2016-08-23  7:54               ` Leizhen (ThunderTown)
2016-08-23 11:19               ` Leizhen (ThunderTown)
2016-08-23 11:30                 ` Will Deacon
2016-08-23 11:50                   ` Leizhen (ThunderTown)

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=20160818160437.GA21343@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).