From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: paulus@samba.org, benh@kernel.crashing.org, mpe@ellerman.id.au,
Laurent Dufour <ldufour@linux.ibm.com>
Cc: Tyrel Datwyler <tyreld@linux.ibm.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Nathan Lynch <nathanl@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5] pseries/drmem: update LMBs after LPM
Date: Wed, 18 Aug 2021 23:38:39 +1000 [thread overview]
Message-ID: <162929391930.3619265.14579706708870831597.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210517090606.56930-1-ldufour@linux.ibm.com>
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 updated because
> there is no way to move a memory block between nodes from the Linux kernel
> point of view.
>
> [...]
Applied to powerpc/next.
[1/1] pseries/drmem: update LMBs after LPM
https://git.kernel.org/powerpc/c/d144f4d5a8a804133d20ff311d7be70bcdbfaac2
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: paulus@samba.org, benh@kernel.crashing.org, mpe@ellerman.id.au,
Laurent Dufour <ldufour@linux.ibm.com>
Cc: Nathan Lynch <nathanl@linux.ibm.com>,
Tyrel Datwyler <tyreld@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>
Subject: Re: [PATCH v5] pseries/drmem: update LMBs after LPM
Date: Wed, 18 Aug 2021 23:38:39 +1000 [thread overview]
Message-ID: <162929391930.3619265.14579706708870831597.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210517090606.56930-1-ldufour@linux.ibm.com>
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 updated because
> there is no way to move a memory block between nodes from the Linux kernel
> point of view.
>
> [...]
Applied to powerpc/next.
[1/1] pseries/drmem: update LMBs after LPM
https://git.kernel.org/powerpc/c/d144f4d5a8a804133d20ff311d7be70bcdbfaac2
cheers
next prev parent reply other threads:[~2021-08-18 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 9:06 [PATCH v5] pseries/drmem: update LMBs after LPM Laurent Dufour
2021-05-17 9:06 ` Laurent Dufour
2021-07-01 8:36 ` Laurent Dufour
2021-07-19 9:10 ` Laurent Dufour
2021-08-03 17:32 ` Nathan Lynch
2021-08-03 17:32 ` Nathan Lynch
2021-08-03 17:34 ` Laurent Dufour
2021-08-03 17:34 ` Laurent Dufour
2021-08-18 13:38 ` Michael Ellerman [this message]
2021-08-18 13:38 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162929391930.3619265.14579706708870831597.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=paulus@samba.org \
--cc=tyreld@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.