[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164668834766.3268493.2965341441709965895.b4-ty@kernel.org>
Date: Mon, 7 Mar 2022 22:03:35 +0000
From: Will Deacon <will@...nel.org>
To: Huang Shijie <shijie@...amperecomputing.com>,
catalin.marinas@....com
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
vgoyal@...hat.com, darren@...amperecomputing.com,
linux-arm-kernel@...ts.infradead.org, dyoung@...hat.com,
zwang@...erecomputing.com, kexec@...ts.infradead.org,
bhe@...hat.com, corbet@....net, linux-kernel@...r.kernel.org,
patches@...erecomputing.com, linux-doc@...r.kernel.org
Subject: Re: [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges
On Wed, 9 Feb 2022 09:26:42 +0000, Huang Shijie wrote:
> The following interrelated ranges are needed by the kdump crash tool:
> MODULES_VADDR ~ MODULES_END,
> VMALLOC_START ~ VMALLOC_END,
> VMEMMAP_START ~ VMEMMAP_END
>
> Since these values change from time to time, it is preferable to export
> them via vmcoreinfo than to change the crash's code frequently.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges
https://git.kernel.org/arm64/c/2369f171d5c5
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists