From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965428AbbI2TKi (ORCPT ); Tue, 29 Sep 2015 15:10:38 -0400 Received: from e23smtp09.au.ibm.com ([202.81.31.142]:38042 "EHLO e23smtp09.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965334AbbI2TKK (ORCPT ); Tue, 29 Sep 2015 15:10:10 -0400 X-Helo: d23dlp03.au.ibm.com X-MailFrom: raghavendra.kt@linux.vnet.ibm.com X-RcptTo: linux-kernel@vger.kernel.org Message-ID: <560AE21E.8040903@linux.vnet.ibm.com> Date: Wed, 30 Sep 2015 00:40:22 +0530 From: Raghavendra K T Organization: IBM User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Nishanth Aravamudan CC: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au, anton@samba.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, cl@linux.com, gkurz@linux.vnet.ibm.com, grant.likely@linaro.org, nikunj@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com Subject: Re: [PATCH RFC 0/5] powerpc:numa Add serial nid support References: <1443378553-2146-1-git-send-email-raghavendra.kt@linux.vnet.ibm.com> <20150928173434.GE48470@linux.vnet.ibm.com> In-Reply-To: <20150928173434.GE48470@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15092919-0033-0000-0000-000002302491 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/28/2015 11:04 PM, Nishanth Aravamudan wrote: > On 27.09.2015 [23:59:08 +0530], Raghavendra K T wrote: [...] >> >> 2) Map the sparse chipid got from device tree to a serial nid at kernel >> level (The idea proposed in this series). >> Pro: It is more natural to handle at kernel level than at lower (OPAL) layer. >> con: The chipid is in device tree no longer the same as nid in kernel > > Is there any debugging/logging? Looks like not -- so how does a sysadmin > map from firmware-provided values to the Linux values? That's going to > make debugging of large systems (PowerVM or otherwise) less than > pleasant, it seems? Possibly you could put something in sysfs? I see 2 things could be done here: 1) while doing dump_numa_cpu_topology() we can dump nid_to_chipid() as additional information. 2) sysfs-> Does /sys/devices/system/node/nodeX/*chipid* looks good. May be we should add only for powerpc or otherwise we need to have chipid = nid populated for other archs. [ I think this change may be done slowly ]