Thread (12 messages) flat view 12 messages, 6 authors, 2016-05-27

[PATCH 3/3] arm64/numa: fix type info

From: Leizhen ThunderTown <hidden>
Date: 2016-05-27 02:36:21
Also in: linux-devicetree, lkml


On 2016/5/27 1:12, David Daney wrote:
The current patch to correct this problem is here:

https://lkml.org/lkml/2016/5/24/679

Since v7 of the ACPI/NUMA patches are likely going to be added to linux-next as soon as the current merge window ends, further simplifications of the informational prints should probably be rebased on top of it.

David Daney
quoted
On Thu, 2016-05-26 at 09:22 -0700, Ganapatrao Kulkarni wrote:
quoted
IIRC, it should be
if (!numa_off)
we want to print this message when we failed to find proper numa configuration.
when numa_off is set, we will not look for any numa configuration.
quoted
+               pr_info("%s\n", "No NUMA configuration found");

OK, I think I also missed some cases.

But my problem still have not been resolved by "https://lkml.org/lkml/2016/5/24/679", see below. I will update my patches base on it.


[    0.000000] NUMA: Adding memblock [0x0 - 0x6affffff] on node 0
[    0.000000] NUMA: parsing numa-distance-map-v1
[    0.000000] NUMA: Warning: invalid memblk node 4 [mem 0x6b000000-0x7fbfffff]		//My numa configuration is incorrect, but not "No ... found"
[    0.000000] No NUMA configuration found						//Above warning is very detail, this can be removed
[    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x00000017ffffffff]
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help