On Mon, 17 May 2021 11:06:06 +0200, Laurent Dufour wrote:
> 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 handled by the kernel, but the memory's node is not
Le 03/08/2021 à 19:32, Nathan Lynch a écrit :
Laurent Dufour writes:
V5:
- Reword the commit's description to address Nathan's comments.
Thanks. Still don't like the global variable usage but:
Reviewed-by: Nathan Lynch
Thanks Nathan,
I don't like either the global variable usage but
Laurent Dufour writes:
> V5:
> - Reword the commit's description to address Nathan's comments.
Thanks. Still don't like the global variable usage but:
Reviewed-by: Nathan Lynch
Hi Michael,
Is there a way to get that patch in 5.14?
Thanks,
Laurent.
Le 17/05/2021 à 11:06, Laurent Dufour a écrit :
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
Hi Michael,
Do you mind taking this patch of 5.14?
Thanks,
Laurent.
Le 17/05/2021 à 11:06, Laurent Dufour a écrit :
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
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 handled by the kernel, but the memory's node is not updated because
there is no way to move a memory block between nodes
