Date: Thu, 7 Jun 2018 10:02:15 -0400 From: Mark Johnston <markj@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r334616 - head/sys/dev/acpica Message-ID: <20180607140215.GB96819@pesky> In-Reply-To: <9b13b9db-f040-809d-0c24-67dc408380ec@FreeBSD.org> References: <201806041456.w54Eu3hB062082@repo.freebsd.org> <9b13b9db-f040-809d-0c24-67dc408380ec@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 07, 2018 at 09:54:01AM -0400, John Baldwin wrote: > On 6/4/18 10:56 AM, Mark Johnston wrote: > > Author: markj > > Date: Mon Jun 4 14:56:02 2018 > > New Revision: 334616 > > URL: https://svnweb.freebsd.org/changeset/base/334616 > > > > Log: > > Fix the NUMA build for non-x86 platforms. > > > > acpi_map_pxm_to_vm_domainid() is currently implemented only on x86. > > > > MFC after: 1 week > > It seems that non-x86 platforms that support NUMA should implement > this function instead. The SRAT table is not x86-specific and ACPI > platforms implementing NUMA will need to provide an SRAT parser to > describe the memory layout to VM and to map _PXM values to the > VM domain values assigned by that mapping. Indeed, this was a small step towards lifting some of the code in x86/acpica/srat.c into the generic driver for use on arm64. In my case I'm looking a ThunderX, which exposes NUMA locality info in both the ofw device tree and the SRAT table. I'm looking at ofw first, and in the meantime I just needed a buildable options NUMA kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180607140215.GB96819>