From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932287AbcE0CgV (ORCPT ); Thu, 26 May 2016 22:36:21 -0400 Received: from szxga03-in.huawei.com ([119.145.14.66]:36628 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932226AbcE0CgU (ORCPT ); Thu, 26 May 2016 22:36:20 -0400 Subject: Re: [PATCH 3/3] arm64/numa: fix type info To: David Daney , Joe Perches References: <1464230639-9852-1-git-send-email-thunder.leizhen@huawei.com> <1464230639-9852-3-git-send-email-thunder.leizhen@huawei.com> <1464280503.16344.40.camel@perches.com> <57472E8C.1050607@gmail.com> CC: Ganapatrao Kulkarni , devicetree , Zefan Li , David Daney , Catalin Marinas , "Xinwei Hu" , Tianhong Ding , "Will Deacon" , linux-kernel , Robert Richter , Rob Herring , Hanjun Guo , Grant Likely , Ganapatrao Kulkarni , Frank Rowand , linux-arm-kernel From: "Leizhen (ThunderTown)" Message-ID: <5747B287.7050309@huawei.com> Date: Fri, 27 May 2016 10:35:51 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <57472E8C.1050607@gmail.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.23.164] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.5747B297.00D0,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: e2f8725edfd4e4675a1a5205c76d0c36 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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]