John Ogness 9227a870b8 scripts/gdb: lx-dmesg: read records individually ... [ Upstream commit deaee2704a ] For the gdb command lx-dmesg, the entire descriptor, info, and text data regions are read into memory before printing any records. For large kernel log buffers, this not only causes a huge delay before seeing any records, but it may also lead to python errors of too much memory allocation. Rather than reading in all these regions in advance, read them as needed and only read the regions for the particular record that is being printed. The gdb macro "dmesg" in Documentation/admin-guide/kdump/gdbmacros.txt already prints out the kernel log buffer like this. Signed-off-by: John Ogness <john.ogness@linutronix.de> Signed-off-by: Petr Mladek <pmladek@suse.com> Link: https://lore.kernel.org/r/874k79c3a9.fsf@jogness.linutronix.de Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-08-17 14:23:56 +02:00
..
linux	scripts/gdb: lx-dmesg: read records individually	2022-08-17 14:23:56 +02:00
Makefile
vmlinux-gdb.py