On 12/25/2023 7:25 PM, Ruipeng Qi wrote:
<+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 :)
Hope you had the same..:-)
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!
In the current state and in simple terms, Qualcomm Minidump can not do
this, Minidump is more of a consumer driver so, what ever gets
registered with it, it can dump. Qualcomm Minidump serves bigger purpose
to dump content in any kind of crash whether it is kernel or non-kernel
like NOC errors/XPUs etc and both kernel/non-kernel entity can register
to it, so we gets dump in any kind of system crash.
One more thing, kernel part of minidump, we are calling it APSS Minidump
has limitation of no of entries so it will be difficult to dump
non-continuous regions after a certain number of registration ~200. However,
we do have a solution in downstream kernel for it like to create a big
CMA buffer and register this buffer with Minidump so that whatever gets
dumped in that buffer gets captured during crash and fill up this buffer
and create elf during panic. I think, similar thing you are also doing
with your OS-minidump.
I have just glanced into your implementation of OS-minidump, it
more of relying on basic concept of RAM content preserved
across boot and later reading it through procfs but this basic
stuff is common to pstore(ram) as well and pstore has file system
support why don't you make your driver as one of pstore record and that
way Qualcomm minidump also gets benefited where entire OS-minidump
record gets registered with Qualcomm minidump and we get this on panic
and you get this via pstorefs.
-Mukesh
Best Regards
Ruipeng
