lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 13 Mar 2017 14:30:46 +0100 From: Borislav Petkov <bp@...en8.de> To: Wei Yang <richard.weiyang@...il.com> Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, tj@...nel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo() On Mon, Feb 06, 2017 at 11:35:29PM +0800, Wei Yang wrote: > numa_nodemask_from_meminfo() is called to set bit according to > numa_meminfo. While the only two places for this call is used to set proper > bit to a copy of numa_nodes_parsed from numa_meminfo. With current code > path, those numa node information in numa_meminfo is a subset of > numa_nodes_parsed. So it is not necessary to set the bits again. > > The following is a code path analysis to prove the numa node information in > numa_meminfo is a subset of numa_nodes_parsed. > > x86_numa_init() > numa_init() > Case 1 > acpi_numa_init() > acpi_parse_memory_affinity() > numa_add_memblk() > node_set(numa_nodes_parsed) > acpi_parse_slit() > numa_nodemask_from_meminfo() > > Case 2 > amd_numa_init() > numa_add_memblk() > node_set(numa_nodes_parsed) > > Case 3 > dummy_numa_init() > node_set(numa_nodes_parsed) > numa_add_memblk() > > numa_register_memblks() > numa_nodemask_from_meminfo() What about of_numa_parse_memory_nodes() ? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists