From: Ruipeng Qi <ruipengqi7@gmail.com>
To: quic_mojha@quicinc.com
Cc: agross@kernel.org, alim.akhtar@samsung.com, andersson@kernel.org,
bmasney@redhat.com, conor+dt@kernel.org, corbet@lwn.net,
gpiccoli@igalia.com, keescook@chromium.org, kernel@quicinc.com,
kgene@kernel.org, konrad.dybcio@linaro.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-remoteproc@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, mathieu.poirier@linaro.org,
matthias.bgg@gmail.com, nm@ti.com, robh+dt@kernel.org,
tony.luck@intel.com, vigneshr@ti.com, qiruipeng@lixiang.com
Subject: RESEND: Re: [Patch v6 03/12] docs: qcom: Add qualcomm minidump guide
Date: Mon, 25 Dec 2023 21:51:53 +0800 [thread overview]
Message-ID: <20231225135153.1408-1-ruipengqi7@gmail.com> (raw)
In-Reply-To: <in-reply-to=1700864395-1479-4-git-send-email-quic_mojha@quicinc.com>
<+How a kernel client driver can register region with minidump
<+------------------------------------------------------------
<+
<+Client driver can use ``qcom_minidump_region_register`` API's to register
<+and ``qcom_minidump_region_unregister`` to unregister their region from
<+minidump driver.
<+
<+Client needs to fill their region by filling ``qcom_minidump_region``
<+structure object which consists of the region name, region's virtual
<+and physical address and its size.
Hi, Mukesh, wish you a good holiday :)
I have the following idea, please help me to assess whether this can be
implemented or not. As we all know, most of the kernel objects are
allocated by the slab sub-system.I wonder if we can dump all memory
keeped by the slab sub-system? If so, we got most of the kernel objects
which will be helpful to fix problems when we run with system issues.
How can we do this? From the description above, I think we should
register one region for each slab, for each slab will have some pages,
and the memory between each slab is non-continuous. As we all
know, there are millions of slabs in the system, so if we dump slabs
in this way, it will introduce a heavy overhead.
I am not very familiar with qualcomm minidump, maybe my thought
is wrong. Looking forward to your reply!
Best Regards
Ruipeng
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2023-12-25 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <in-reply-to=1700864395-1479-4-git-send-email-quic_mojha@quicinc.com>
2023-12-25 13:51 ` Ruipeng Qi [this message]
2023-11-24 22:19 [Patch v6 03/12] docs: qcom: Add qualcomm minidump guide Mukesh Ojha
2023-12-25 13:55 ` RESEND: " Ruipeng Qi
2024-01-03 15:27 ` Mukesh Ojha
2024-01-08 15:34 ` Ruipeng Qi
2024-01-09 8:27 ` Mukesh Ojha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231225135153.1408-1-ruipengqi7@gmail.com \
--to=ruipengqi7@gmail.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@quicinc.com \
--cc=kgene@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=nm@ti.com \
--cc=qiruipeng@lixiang.com \
--cc=quic_mojha@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).