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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 7 Jun 2017 12:28:06 -0500
From:   Michael Bringmann <mwb@...ux.vnet.ibm.com>
To:     Michael Ellerman <mpe@...erman.id.au>,
        Reza Arbab <arbab@...ux.vnet.ibm.com>
Cc:     Balbir Singh <bsingharora@...il.com>, linux-kernel@...r.kernel.org,
        Paul Mackerras <paulus@...ba.org>,
        "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
        Bharata B Rao <bharata@...ux.vnet.ibm.com>,
        Shailendra Singh <shailendras@...dia.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        linuxppc-dev@...ts.ozlabs.org,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Michael Bringmann from Kernel Team <mbringm@...ibm.com>
Subject: RESEND Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node
 assoc


Here is the information from 2 different kernels.  I have not been able to retrieve
the information matching yesterday's attachments, yet, as those dumps were
acquired in April.
 
Attached please find 2 dumps of similar material from kernels running with my
current patches (Linux 4.4, Linux 4.12).

On 06/07/2017 07:08 AM, Michael Ellerman wrote:
> Michael Bringmann <mwb@...ux.vnet.ibm.com> writes:
> 
>> On 06/06/2017 04:48 AM, Michael Ellerman wrote:
>>> Michael Bringmann <mwb@...ux.vnet.ibm.com> writes:
>>>> On 06/01/2017 04:36 AM, Michael Ellerman wrote:
>>>>> Do you actually see mention of nodes 0 and 8 in the dmesg?
>>>>
>>>> When the 'numa.c' code is built with debug messages, and the system was
>>>> given that configuration by pHyp, yes, I did.
>>>>
>>>>> What does it say?
>>>>
>>>> The debug message for each core thread would be something like,
>>>>
>>>>     removing cpu 64 from node 0
>>>>     adding cpu 64 to node 8
>>>>
>>>> repeated for all 8 threads of the CPU, and usually with the messages
>>>> for all of the CPUs coming out intermixed on the console/dmesg log.
>>>
>>> OK. I meant what do you see at boot.
>>
>> Here is an example with nodes 0,2,6,7, node 0 starts out empty:
>>
>> [    0.000000] Initmem setup node 0
>> [    0.000000]   NODE_DATA [mem 0x3bff7d6300-0x3bff7dffff]
>> [    0.000000]     NODE_DATA(0) on node 7
>> [    0.000000] Initmem setup node 2 [mem 0x00000000-0x13ffffffff]
>> [    0.000000]   NODE_DATA [mem 0x13ffff6300-0x13ffffffff]
>> [    0.000000] Initmem setup node 6 [mem 0x1400000000-0x34afffffff]
>> [    0.000000]   NODE_DATA [mem 0x34afff6300-0x34afffffff]
>> [    0.000000] Initmem setup node 7 [mem 0x34b0000000-0x3bffffffff]
>> [    0.000000]   NODE_DATA [mem 0x3bff7cc600-0x3bff7d62ff]
>>
>> [    0.000000] Zone ranges:
>> [    0.000000]   DMA      [mem 0x0000000000000000-0x0000003bffffffff]
>> [    0.000000]   DMA32    empty
>> [    0.000000]   Normal   empty
>> [    0.000000] Movable zone start for each node
>> [    0.000000] Early memory node ranges
>> [    0.000000]   node   2: [mem 0x0000000000000000-0x00000013ffffffff]
>> [    0.000000]   node   6: [mem 0x0000001400000000-0x00000034afffffff]
>> [    0.000000]   node   7: [mem 0x00000034b0000000-0x0000003bffffffff]
>> [    0.000000] Could not find start_pfn for node 0
>> [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000000000000]
>> [    0.000000] Initmem setup node 2 [mem 0x0000000000000000-0x00000013ffffffff]
>> [    0.000000] Initmem setup node 6 [mem 0x0000001400000000-0x00000034afffffff]
>> [    0.000000] Initmem setup node 7 [mem 0x00000034b0000000-0x0000003bffffffff]
>> [    0.000000] percpu: Embedded 3 pages/cpu @c000003bf8000000 s155672 r0 d40936 u262144
>> [    0.000000] Built 4 zonelists in Node order, mobility grouping on.  Total pages: 3928320
>>
>> and,
>>
>> [root@...alpine2-lp20 ~]# numactl --hardware
>> available: 4 nodes (0,2,6-7)
>> node 0 cpus:
>> node 0 size: 0 MB
>> node 0 free: 0 MB
>> node 2 cpus: 16 17 18 19 20 21 22 23 32 33 34 35 36 37 38 39 56 57 58 59 60 61 62 63
>> node 2 size: 81792 MB
>> node 2 free: 81033 MB
>> node 6 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 24 25 26 27 28 29 30 31 40 41 42 43 44 45 46 47
>> node 6 size: 133743 MB
>> node 6 free: 133097 MB
>> node 7 cpus: 48 49 50 51 52 53 54 55
>> node 7 size: 29877 MB
>> node 7 free: 29599 MB
>> node distances:
>> node   0   2   6   7
>>   0:  10  40  40  40
>>   2:  40  10  40  40
>>   6:  40  40  10  20
>>   7:  40  40  20  10
>> [root@...alpine2-lp20 ~]#
> 
> What kernel is that running?
> 
> And can you show me the full ibm,dynamic-memory and lookup-arrays
> properties for that system?
> 
> cheers
> 
> 

-- 
Michael W. Bringmann
Linux Technology Center
IBM Corporation
Tie-Line  363-5196
External: (512) 286-5196
Cell:       (512) 466-0650
mwb@...ux.vnet.ibm.com

View attachment "1.linux4.12-3nodes.txt" of type "text/plain" (4480 bytes)

View attachment "2.linux4.4-4nodes.txt" of type "text/plain" (88606 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ