aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/fpga/zynq-fpga.c
diff options
context:
space:
mode:
authorSteven Rostedt (Google) <[email protected]>2024-03-05 00:13:42 +0000
committerSteven Rostedt (Google) <[email protected]>2024-03-06 18:27:00 +0000
commit6f42249fecb94dfb6514ed241475f748c03d62fb (patch)
treed112fcb0830155a203ba7e5bed61d6cd7bb720f9 /drivers/fpga/zynq-fpga.c
parenttracing: Remove precision vsnprintf() check from print event (diff)
downloadkernel-6f42249fecb94dfb6514ed241475f748c03d62fb.tar.gz
kernel-6f42249fecb94dfb6514ed241475f748c03d62fb.zip
tracing: Limit trace_seq size to just 8K and not depend on architecture PAGE_SIZE
The trace_seq buffer is used to print out entire events. It's typically set to PAGE_SIZE * 2 as there's some events that can be quite large. As a side effect, writes to trace_marker is limited by both the size of the trace_seq buffer as well as the ring buffer's sub-buffer size (which is a power of PAGE_SIZE). By limiting the trace_seq size, it also limits the size of the largest string written to trace_marker. trace_seq does not need to be dependent on PAGE_SIZE like the ring buffer sub-buffers need to be. Hard code it to 8K which is PAGE_SIZE * 2 on most architectures. This will also limit the size of trace_marker on those architectures with greater than 4K PAGE_SIZE. Link: https://lore.kernel.org/all/[email protected]/ Link: https://lore.kernel.org/linux-trace-kernel/[email protected] Cc: Masami Hiramatsu <[email protected]> Cc: Mathieu Desnoyers <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Sachin Sant <[email protected]> Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'drivers/fpga/zynq-fpga.c')
0 files changed, 0 insertions, 0 deletions