[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c0a0daf4-e9e3-4152-8e5e-c7b52a30dae9@linaro.org>
Date: Mon, 22 Sep 2025 11:01:51 +0100
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: Eugen Hristev <eugen.hristev@...aro.org>, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, tglx@...utronix.de,
andersson@...nel.org, pmladek@...e.com, rdunlap@...radead.org,
corbet@....net, david@...hat.com, mhocko@...e.com
Cc: mukesh.ojha@....qualcomm.com, linux-arm-kernel@...ts.infradead.org,
linux-hardening@...r.kernel.org, jonechou@...gle.com, rostedt@...dmis.org,
linux-doc@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [RFC][PATCH v3 15/16] kmemdump: Add Kinfo backend driver
Hi,
On 9/12/25 4:08 PM, Eugen Hristev wrote:
> Add Kinfo backend driver.
> This backend driver will select only regions of interest for the firmware,
> and it copy those into a shared memory area that is supplied via OF.
> The firmware is only interested in addresses for some symbols.
> The list format is kinfo-compatible, with devices like Google Pixel phone.
>
> Signed-off-by: Eugen Hristev <eugen.hristev@...aro.org>
> ---
> MAINTAINERS | 5 +
> mm/kmemdump/Kconfig.debug | 13 ++
> mm/kmemdump/Makefile | 1 +
> mm/kmemdump/kinfo.c | 293 ++++++++++++++++++++++++++++++++++++++
> 4 files changed, 312 insertions(+)
> create mode 100644 mm/kmemdump/kinfo.c
I tested the series on pixel 6 and I could see the backtraces correctly
decoded by the bootloader:
Tested-by: Tudor Ambarus <tudor.ambarus@...aro.org>
Thanks!
Powered by blists - more mailing lists