[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0195eb73-99ae-fec2-3e11-2cb9e6677926@huawei.com>
Date: Sat, 31 Aug 2019 16:57:04 +0800
From: Yunsheng Lin <linyunsheng@...wei.com>
To: David Miller <davem@...emloft.net>
CC: <catalin.marinas@....com>, <will@...nel.org>, <mingo@...hat.com>,
<bp@...en8.de>, <rth@...ddle.net>, <ink@...assic.park.msu.ru>,
<mattst88@...il.com>, <benh@...nel.crashing.org>,
<paulus@...ba.org>, <mpe@...erman.id.au>,
<heiko.carstens@...ibm.com>, <gor@...ux.ibm.com>,
<borntraeger@...ibm.com>, <ysato@...rs.sourceforge.jp>,
<dalias@...c.org>, <ralf@...ux-mips.org>, <paul.burton@...s.com>,
<jhogan@...nel.org>, <jiaxun.yang@...goat.com>,
<chenhc@...ote.com>, <akpm@...ux-foundation.org>,
<rppt@...ux.ibm.com>, <anshuman.khandual@....com>,
<tglx@...utronix.de>, <cai@....pw>, <robin.murphy@....com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <hpa@...or.com>, <x86@...nel.org>,
<dave.hansen@...ux.intel.com>, <luto@...nel.org>,
<peterz@...radead.org>, <len.brown@...el.com>, <axboe@...nel.dk>,
<dledford@...hat.com>, <jeffrey.t.kirsher@...el.com>,
<linux-alpha@...r.kernel.org>, <nfont@...ux.vnet.ibm.com>,
<naveen.n.rao@...ux.vnet.ibm.com>, <mwb@...ux.vnet.ibm.com>,
<linuxppc-dev@...ts.ozlabs.org>, <linux-s390@...r.kernel.org>,
<linux-sh@...r.kernel.org>, <sparclinux@...r.kernel.org>,
<tbogendoerfer@...e.de>, <linux-mips@...r.kernel.org>,
<linuxarm@...wei.com>
Subject: Re: [PATCH v2 7/9] sparc64: numa: check the node id consistently for
sparc64
On 2019/8/31 14:53, David Miller wrote:
> From: Yunsheng Lin <linyunsheng@...wei.com>
> Date: Sat, 31 Aug 2019 13:58:21 +0800
>
>> According to Section 6.2.14 from ACPI spec 6.3 [1], the setting
>> of proximity domain is optional, as below:
>
> What in the world does the ACPI spec have to do with sparc64 NUMA
> node ID checking?
I am not sure I understand your question fully here.
Here is my issue when the bios does not implement the proximity domain
of a device because the feature is optional according to the ACPI spec,
the dev_to_node(dev) return -1, which causes out of bound access when
using the value to get the device's cpu mask by calling cpumask_of_node.
Did you mean sparc64 system does not has ACPI, the device's node id will
not specified by ACPI, so the ACPI is unrelated here?
Or did you mean the commit log is not clear enough to justify the change?
Or did you mean this problem should be fixed in somewhere else?
Any detail advice and suggestion will be very helpful, thanks.
>
> .
>
Powered by blists - more mailing lists