[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190831.130250.1236116087422472663.davem@davemloft.net>
Date: Sat, 31 Aug 2019 13:02:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: linyunsheng@...wei.com
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
From: Yunsheng Lin <linyunsheng@...wei.com>
Date: Sat, 31 Aug 2019 16:57:04 +0800
> 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?
Yes, sparc64 never has and never will have ACPI.
This is also true for several other platforms where you have made this
change.
The assumption of your entire patch set is that the semantics of the
NUMA node ID are somehow completely defined by ACPI semantics. Which
is not true.
Powered by blists - more mailing lists