[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yg4jhWnfYIGYBLs/@hsj>
Date: Thu, 17 Feb 2022 10:29:25 +0000
From: Huang Shijie <shijie@...amperecomputing.com>
To: Will Deacon <will@...nel.org>
Cc: catalin.marinas@....com, bhe@...hat.com, vgoyal@...hat.com,
dyoung@...hat.com, corbet@....net, kexec@...ts.infradead.org,
linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, zwang@...erecomputing.com,
patches@...erecomputing.com, darren@...amperecomputing.com,
k-hagio-ab@....com, lijiang@...hat.com
Subject: Re: [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP
ranges
On Thu, Feb 17, 2022 at 10:02:03AM +0000, Huang Shijie wrote:
> > Thanks for digging up all of the kernel memory map changes and taking the
> > time to explain the macros. However, all I'm really after is something in
> > the commit message of the patch which explains what is broken without this
> This kernel patch does not break anything.
I mean this kernel patch is not a bugfix, it is just make the ARM64 ecosystem
(including the Crash) a little better..
The Crash can just parse out the MODULES/VMALLOC/VMALLOC ranges from the vmcore file,
no need to calculate them in a very _hard_ way.
Thanks
Huang Shijie
Powered by blists - more mailing lists