rpms/kexec-tools
7
0
Fork 0
Code Issues Pull Requests Releases Activity

Revert "Remove trace_buf_size and trace_event from the kernel bootparameters of the kdump kernel"

Browse Source 
There is a mechanism to keep memory consumption minimum, i.e. equal
to trace_buf_size=1, until tracing by ftrace is actually started:

    tracing: keep ring buffer to minimum size till used
    73c5162aa3

Since ftrace is usually never used in the kdump 2nd kernel, the kdump
2nd kernel behaves in the same way with or without trace_buf_size=1.
So the issue which the patch want to solve never exists. Let's revert
the patch for better maintainance and avoid confusion.

ref link: https://bugzilla.redhat.com/show_bug.cgi?id=2034501#c20

This reverts commit f39000f.

Signed-off-by: Tao Liu <ltao@redhat.com>
Acked-by: Coiby Xu <coxu@redhat.com>
This commit is contained in:
Tao Liu 2022-01-21 16:08:47 +08:00 committed by Coiby Xu
parent 748eb3a2a6
commit 99de77bba7
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
kdump-lib.sh
View File

@ -782,10 +782,6 @@ prepare_cmdline()
fi
done
# Remove trace_buf_size, trace_event
cmdline=$(remove_cmdline_param "$cmdline" trace_buf_size trace_event)
cmdline="${cmdline} trace_buf_size=1"
echo "$cmdline"
}