From: Will Deacon <will@kernel.org>
To: Chris Goldsworthy <quic_cgoldswo@quicinc.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
Georgi Djakov <quic_c_gdjako@quicinc.com>,
Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: arm64: mm: update max_pfn after memory hotplug
Date: Wed, 29 Sep 2021 18:48:27 +0100 [thread overview]
Message-ID: <163293186685.928897.8618689831730989496.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1632853776.git.quic_cgoldswo@quicinc.com>
On Tue, 28 Sep 2021 11:51:48 -0700, Chris Goldsworthy wrote:
> Follow up of RFC patch:
>
> https://lore.kernel.org/linux-mm/a3bf84c4-8f35-f273-145c-55928a06f332@quicinc.com/T/#m219937b1acdd40318bbe90ab39f187804775eb74
>
> On arm64 we set max_pfn at boot in arch/arm64/mm/init.c. If you
> hotplug in memory after booting up, max_pfn is not updated. This
> breaks diagnostic functions executed from user space like
> read_page_owner():
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: mm: update max_pfn after memory hotplug
https://git.kernel.org/arm64/c/8fac67ca236b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-09-29 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 18:51 Chris Goldsworthy
2021-09-28 18:51 ` [PATCH] " Chris Goldsworthy
2021-09-28 19:34 ` Georgi Djakov
2021-10-01 6:38 ` Anshuman Khandual
2021-10-01 8:39 ` David Hildenbrand
2021-10-01 8:52 ` Anshuman Khandual
2021-09-29 17:48 ` Will Deacon [this message]
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=163293186685.928897.8618689831730989496.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=quic_cgoldswo@quicinc.com \
--cc=quic_sudaraja@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox