From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Geetika Moolchandani <Geetika.Moolchandani1@ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] powerpc/numa: Handle partially initialized numa nodes
Date: Sun, 10 Apr 2022 22:27:07 +1000 [thread overview]
Message-ID: <164959362780.1306388.11008061889619945324.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220330135123.1868197-1-srikar@linux.vnet.ibm.com>
On Wed, 30 Mar 2022 19:21:23 +0530, Srikar Dronamraju wrote:
> With commit 09f49dca570a ("mm: handle uninitialized numa nodes
> gracefully") NODE_DATA for even a memoryless/cpuless node is partially
> initialized at boot time.
>
> Before onlining the node, current Powerpc code checks for NODE_DATA to
> be NULL. However since NODE_DATA is partially initialized, this check
> will end up always being false.
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc/numa: Handle partially initialized numa nodes
https://git.kernel.org/powerpc/c/e4ff77598a109bd36789ad5e80aba66fc53d0ffb
cheers
prev parent reply other threads:[~2022-04-10 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 13:51 [PATCH] powerpc/numa: Handle partially initialized numa nodes Srikar Dronamraju
2022-03-30 13:59 ` Michal Hocko
2022-03-30 14:04 ` Oscar Salvador
2022-04-05 4:41 ` Mike Rapoport
2022-04-06 16:19 ` Oscar Salvador
2022-04-08 12:25 ` Srikar Dronamraju
2022-04-10 11:28 ` Michael Ellerman
2022-04-11 8:00 ` Oscar Salvador
2022-04-11 6:29 ` Geetika Moolchandani1
2022-04-10 12:27 ` Michael Ellerman [this message]
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=164959362780.1306388.11008061889619945324.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=Geetika.Moolchandani1@ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=srikar@linux.vnet.ibm.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).