Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-05-04 Thread Laurent Dufour
Le 03/05/2021 à 22:44, Tyrel Datwyler a écrit : On 5/3/21 10:28 AM, Laurent Dufour wrote: Le 01/05/2021 à 01:58, Tyrel Datwyler a écrit : On 4/30/21 9:13 AM, Laurent Dufour wrote: Le 29/04/2021 à 21:12, Tyrel Datwyler a écrit : On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote: Laurent Dufour writ

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-05-03 Thread Tyrel Datwyler
On 5/3/21 10:28 AM, Laurent Dufour wrote: > Le 01/05/2021 à 01:58, Tyrel Datwyler a écrit : >> On 4/30/21 9:13 AM, Laurent Dufour wrote: >>> Le 29/04/2021 à 21:12, Tyrel Datwyler a écrit : On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote: > Laurent Dufour writes: > Snip >> >> As of today

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-05-03 Thread Laurent Dufour
Le 01/05/2021 à 01:58, Tyrel Datwyler a écrit : On 4/30/21 9:13 AM, Laurent Dufour wrote: Le 29/04/2021 à 21:12, Tyrel Datwyler a écrit : On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote: Laurent Dufour writes: After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-30 Thread Tyrel Datwyler
On 4/30/21 9:13 AM, Laurent Dufour wrote: > Le 29/04/2021 à 21:12, Tyrel Datwyler a écrit : >> On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote: >>> Laurent Dufour writes: >>> After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by the hypervisor in the case the

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-30 Thread Laurent Dufour
Le 29/04/2021 à 21:12, Tyrel Datwyler a écrit : On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote: Laurent Dufour writes: After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by the hypervisor in the case the NUMA topology of the LPAR's memory is updated. This is caug

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-29 Thread Tyrel Datwyler
On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote: > Laurent Dufour writes: > >> After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be >> updated by the hypervisor in the case the NUMA topology of the LPAR's >> memory is updated. >> >> This is caught by the kernel, but the memory's

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-29 Thread Laurent Dufour
Le 29/04/2021 à 12:27, Aneesh Kumar K.V a écrit : Laurent Dufour writes: After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by the hypervisor in the case the NUMA topology of the LPAR's memory is updated. This is caught by the kernel, but the memory's node is

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-29 Thread Laurent Dufour
Le 29/04/2021 à 13:31, Laurent Dufour a écrit : Le 29/04/2021 à 12:27, Aneesh Kumar K.V a écrit : Laurent Dufour writes: After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by the hypervisor in the case the NUMA topology of the LPAR's memory is updated. This i

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-29 Thread Laurent Dufour
Le 29/04/2021 à 12:27, Aneesh Kumar K.V a écrit : Laurent Dufour writes: After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by the hypervisor in the case the NUMA topology of the LPAR's memory is updated. This is caught by the kernel, but the memory's node is

Re: [PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-29 Thread Aneesh Kumar K.V
Laurent Dufour writes: > After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be > updated by the hypervisor in the case the NUMA topology of the LPAR's > memory is updated. > > This is caught by the kernel, but the memory's node is updated because > there is no way to move a

[PATCH v3] pseries/drmem: update LMBs after LPM

2021-04-28 Thread Laurent Dufour
After a LPM, the device tree node ibm,dynamic-reconfiguration-memory may be updated by the hypervisor in the case the NUMA topology of the LPAR's memory is updated. This is caught by the kernel, but the memory's node is updated because there is no way to move a memory block between nodes. If late