summaryrefslogtreecommitdiff
path: root/kernel/trace/trace_probe.c
diff options
context:
space:
mode:
authorVincent Donnefort <vdonnefort@google.com>2026-08-13 14:11:49 +0100
committerSteven Rostedt <rostedt@goodmis.org>2026-08-14 13:26:07 -0400
commit472ac478b14d940b555153e50f3a34ac1c5e71ff (patch)
tree950af283de143546d4cb6d388e033e214f5d6a14 /kernel/trace/trace_probe.c
parente743527c5bfdceda1095bc0a9e596e2aebb6a9c3 (diff)
ring-buffer: Dynamically calculate max_data_size
The ring buffer order can be dynamically modified and temporarily disables writing to do so. It is therefore safe to use the updated value to calculate the maximum event size which can be written onto the ring buffer. However, notice it is hardly making any difference for trace_marker because of the TRACE_MARKER_MAX_SIZE limit. For an 8KiB subbuf size, trace_marker can take 4096 characters while it can 'only' take 4054 bytes for smaller subbufs. Link: https://patch.msgid.link/20260813131152.3589632-8-vdonnefort@google.com Signed-off-by: Vincent Donnefort <vdonnefort@google.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_probe.c')
0 files changed, 0 insertions, 0 deletions