Received-SPF: pass (google.com: domain of linux-kernel+bounces-10472-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Precedence: bulk
MIME-Version: 1.0
References: <20231221130930.32634-1-ruipengqi7@gmail.com> <e9aa311f-6f13-410e-bb35-20320275668c@linaro.org>
 <CADHLONGLZaZT4Ot56AnxOf=ROrTWvge5=NUx5uqKqJhpJibfOQ@mail.gmail.com> <6fe05804-da74-45cd-a6f1-df4644671d99@linaro.org>
In-Reply-To: <6fe05804-da74-45cd-a6f1-df4644671d99@linaro.org>
From: ruipeng qi <ruipengqi7@gmail.com>
Date: Sat, 23 Dec 2023 23:13:22 +0800
Message-ID: <CADHLONE2YnBJGJUp2-vn_XEpc7+quTMWF7y1zpV0ygeL2VpQxA@mail.gmail.com>
Subject: Re: [PATCH 1/7] [RFC PATCH 1/7] osdump: Add one new os minidump module
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: catalin.marinas@arm.com, will@kernel.org, bhe@redhat.com, 
	vgoyal@redhat.com, dyoung@redhat.com, linux-kernel@vger.kernel.org, 
	kexec@lists.infradead.org, zalbassam@google.com, dianders@chromium.org, 
	mark.rutland@arm.com, lecopzer.chen@mediatek.com, maz@kernel.org, 
	arnd@arndb.de, yury.norov@gmail.com, brauner@kernel.org, mcgrof@kernel.org, 
	maninder1.s@samsung.com, michael.christie@oracle.com, samitolvanen@google.com, 
	linux-arm-kernel@lists.infradead.org, qiruipeng@lixiang.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 23, 2023 at 10:23=E2=80=AFPM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:

> > Qcom minidump can dump some logs like dmsg, some status like IRQ or
> > Run queue. This can help to learn some information when the issue occur=
s,
> > which will help to find out the root cause. But what it dumps are limit=
ed, it
> > doesn't dump w and lock if they are not local data.
>
> So add missing features to it. I don't think you got my comment and keep
> arguing on the same thing repeated for upstream submissions many times.
> We do not want multiple vendor solutions. Every vendor wants his work
> and does not care about integrating or reusing other pieces.
>
> >
> > For osdump, it dumps objects stored in slab, datas in bss, data segment=
s,
> > some data alloced with memblock, data stored in local stack, and so on.
> > In a word, it dumps almost all of the key data in the kernel. Besides, =
you
> > can use the crash tool to analyze the dump file.
>
> I don't see a problem why minidump cannot do it.
Qcom minidump allows one kernel client to register its region to dump, and =
then
driver will create and maintain one elf head for it.
But osdump will dump thousands of non-continuous regions. If you register o=
ne
by one, and add an elf head for each, it will cause heavy overhead. So it s=
tore
data in binary, and reassemble a standard elf format file offline for debug=
.

Sir, I am not really familiar with Qcom minidump, and some options may be w=
rong.
But do you think it is ok to integrate osdump to Qcom? Looking forward to y=
our
suggestions!

Best Regards
Ruipeng