On 12/23/2023 9:00 PM, ruipeng qi wrote:
On Sat, Dec 23, 2023 at 11:13 PM ruipeng qi <ruipengqi7@xxxxxxxxx> wrote:
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 one
by one, and add an elf head for each, it will cause heavy overhead. So it store
data in binary, and reassemble a standard elf format file offline for debug.
Osdump will only dump useful data, which may have been allocated before but
freed now. In a word, useful data are changing all the time. I think this is not
suitable for Qcom minidump's framework。
Hey @ruipeng,
I like the idea, However, as i already said here
https://lore.kernel.org/lkml/520e377d-e990-c185-4a20-07806873e506@xxxxxxxxxxx/
This looks more close to pstore ramoops based on Ram backend, as your
entire thing is based on RAM content to be preserved across boot and
that way it aligns to pstore ramoops concept.
Also most of the stuff like compression is already available in pstore.
So, let me know if you think that way, will be happy to collaborate and
test this.
-Mukesh
Best Regards
Ruipeng
_______________________________________________
kexec mailing list
kexec@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/kexec
