[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5ed2518b-6e90-4f70-9835-d7cf0600777a@quicinc.com>
Date: Fri, 9 May 2025 10:31:17 -0700
From: Trilok Soni <quic_tsoni@...cinc.com>
To: Eugen Hristev <eugen.hristev@...aro.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>, <andersson@...nel.org>
CC: <linux-doc@...r.kernel.org>, <corbet@....net>, <tglx@...utronix.de>,
<mingo@...hat.com>, <rostedt@...dmis.org>, <john.ogness@...utronix.de>,
<senozhatsky@...omium.org>, <pmladek@...e.com>, <peterz@...radead.org>,
<mojha@....qualcomm.com>, <linux-arm-kernel@...ts.infradead.org>,
<vincent.guittot@...aro.org>, <konradybcio@...nel.org>,
<dietmar.eggemann@....com>, <juri.lelli@...hat.com>
Subject: Re: [RFC][PATCH 01/14] Documentation: add kmemdump
On 4/22/2025 4:31 AM, Eugen Hristev wrote:
> Signed-off-by: Eugen Hristev <eugen.hristev@...aro.org>
> ---
> Documentation/debug/index.rst | 17 +++++++
> Documentation/debug/kmemdump.rst | 77 ++++++++++++++++++++++++++++++++
> 2 files changed, 94 insertions(+)
> create mode 100644 Documentation/debug/index.rst
> create mode 100644 Documentation/debug/kmemdump.rst
>
> diff --git a/Documentation/debug/index.rst b/Documentation/debug/index.rst
> new file mode 100644
> index 000000000000..9a9365c62f02
> --- /dev/null
> +++ b/Documentation/debug/index.rst
> @@ -0,0 +1,17 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +===
> +kmemdump
> +===
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + kmemdump
> +
> +.. only:: subproject and html
> +
> + Indices
> + =======
> +
> + * :ref:`genindex`
> diff --git a/Documentation/debug/kmemdump.rst b/Documentation/debug/kmemdump.rst
> new file mode 100644
> index 000000000000..dfee755a1be1
> --- /dev/null
> +++ b/Documentation/debug/kmemdump.rst
> @@ -0,0 +1,77 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +==========================
> +kmemdump
> +==========================
> +
> +This document provides information about the kmemdump feature.
> +
> +Overview
> +========
> +
> +kmemdump is a mechanism that allows any driver or producer to register a
> +chunk of memory into kmemdump, to be used at a later time for a specific
> +purpose like debugging or memory dumping.
> +
> +kmemdump allows a backend to be connected, this backend interfaces a
> +specific hardware that can debug or dump the memory registered into
> +kmemdump.
> +
> +kmemdump Internals
> +=============
I feel that we are missing to explain "what you need from your firmware"
to support kmemdump on your platform. We should add that section and
given an example on how Qualcomm does it in their firmware etc;
--
---Trilok Soni
Powered by blists - more mailing lists