John Ogness deaee2704a scripts/gdb: lx-dmesg: read records individually ... 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		2021-12-16 15:52:38 +01:00
..
.gitignore
__init__.py
clk.py
config.py
constants.py.in
cpus.py	scripts/gdb: add lx_current support for arm64	2021-05-07 00:26:33 -07:00
device.py
dmesg.py	scripts/gdb: lx-dmesg: read records individually	2021-12-16 15:52:38 +01:00
genpd.py
lists.py	scripts/gdb: fix list_for_each	2021-02-26 09:41:05 -08:00
Makefile	kbuild: use always-y instead of extra-y	2021-02-16 12:01:45 +09:00
modules.py
proc.py	scripts/gdb/proc: add struct mount & struct super_block addr in lx-mounts command	2020-10-16 11:11:22 -07:00
rbtree.py
symbols.py	scripts/gdb: handle split debug for vmlinux	2021-11-09 10:02:52 -08:00
tasks.py	scripts/gdb/tasks: add headers and improve spacing format	2020-10-16 11:11:22 -07:00
timerlist.py
utils.py