aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorSteven Rostedt <[email protected]>2024-10-07 13:16:53 -0400
committerJonathan Corbet <[email protected]>2024-10-14 09:50:30 -0600
commitf7e1d19105b20f23f2ffb6d4949bb2a20bd56da0 (patch)
tree4721b7659e7b5585a9b5d337a370e80706f0c352 /tools/perf/scripts/python/event_analyzing_sample.py
parentf3904bb70aab5e4067eed53869963a919b23a9d6 (diff)
Documentation/tracing: Mention that RESET_ATTACK_MITIGATION can clear memory
At the 2024 Linux Plumbers Conference, I was talking with Hans de Goede about the persistent buffer to display traces from previous boots. He mentioned that UEFI can clear memory. In my own tests I have not seen this. He later informed me that it requires the config option: CONFIG_RESET_ATTACK_MITIGATION It appears that setting this will allow the memory to be cleared on boot up, which will definitely clear out the trace of the previous boot. Add this information under the trace_instance in kernel-parameters.txt to let people know that this can cause issues. Link: https://lore.kernel.org/all/[email protected]/ Reported-by: Hans de Goede <[email protected]> Reviewed-by: Hans de Goede <[email protected]> Acked-by: Ard Biesheuvel <[email protected]> Signed-off-by: Steven Rostedt (Google) <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions