From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: David Daney <ddaney.cavm@gmail.com>, Joe Perches <joe@perches.com>
Cc: Ganapatrao Kulkarni <gpkulkarni@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
Zefan Li <lizefan@huawei.com>,
David Daney <david.daney@cavium.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"Xinwei Hu" <huxinwei@huawei.com>,
Tianhong Ding <dingtianhong@huawei.com>,
"Will Deacon" <will.deacon@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Robert Richter <rrichter@cavium.com>,
Rob Herring <robh+dt@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Grant Likely <grant.likely@linaro.org>,
Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64/numa: fix type info
Date: Fri, 27 May 2016 10:35:51 +0800 [thread overview]
Message-ID: <5747B287.7050309@huawei.com> (raw)
In-Reply-To: <57472E8C.1050607@gmail.com>
On 2016/5/27 1:12, David Daney wrote:
> The current patch to correct this problem is here:
>
> https://lkml.org/lkml/2016/5/24/679
>
> Since v7 of the ACPI/NUMA patches are likely going to be added to linux-next as soon as the current merge window ends, further simplifications of the informational prints should probably be rebased on top of it.
>
> David Daney
>
>> On Thu, 2016-05-26 at 09:22 -0700, Ganapatrao Kulkarni wrote:
>>> IIRC, it should be
>>> if (!numa_off)
>>> we want to print this message when we failed to find proper numa configuration.
>>> when numa_off is set, we will not look for any numa configuration.
>>>
>>>>
>>>> + pr_info("%s\n", "No NUMA configuration found");
>>
OK, I think I also missed some cases.
But my problem still have not been resolved by "https://lkml.org/lkml/2016/5/24/679", see below. I will update my patches base on it.
[ 0.000000] NUMA: Adding memblock [0x0 - 0x6affffff] on node 0
[ 0.000000] NUMA: parsing numa-distance-map-v1
[ 0.000000] NUMA: Warning: invalid memblk node 4 [mem 0x6b000000-0x7fbfffff] //My numa configuration is incorrect, but not "No ... found"
[ 0.000000] No NUMA configuration found //Above warning is very detail, this can be removed
[ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x00000017ffffffff]
prev parent reply other threads:[~2016-05-27 2:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 2:43 [PATCH 1/3] of/numa: remove a duplicated pr_debug information Zhen Lei
2016-05-26 2:43 ` [PATCH 2/3] of/numa: fix a memory@ dt node can only contains one memory block Zhen Lei
2016-05-26 13:13 ` Rob Herring
2016-05-27 3:36 ` Leizhen (ThunderTown)
2016-05-27 4:20 ` Rob Herring
2016-05-27 7:04 ` Leizhen (ThunderTown)
2016-05-27 16:07 ` David Daney
2016-05-26 2:43 ` [PATCH 3/3] arm64/numa: fix type info Zhen Lei
2016-05-26 16:22 ` Ganapatrao Kulkarni
2016-05-26 16:35 ` Joe Perches
2016-05-26 17:12 ` David Daney
2016-05-27 2:35 ` Leizhen (ThunderTown) [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=5747B287.7050309@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dingtianhong@huawei.com \
--cc=frowand.list@gmail.com \
--cc=gkulkarni@caviumnetworks.com \
--cc=gpkulkarni@gmail.com \
--cc=grant.likely@linaro.org \
--cc=guohanjun@huawei.com \
--cc=huxinwei@huawei.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=robh+dt@kernel.org \
--cc=rrichter@cavium.com \
--cc=will.deacon@arm.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