60a9a7b17b
Reduce the trace buffer size further Bug: 383121598 Test: Manually observed the optimized trace settings Flag: EXEMPT, optimize interrupt tracing. Change-Id: Id6e02df4d73a97b99a019b210dbd508b115462fc Signed-off-by: Chintan Pandya <chintanpandya@google.com>
17 lines
1 KiB
Text
17 lines
1 KiB
Text
on init
|
|
# With permissions 666, trace was not captured in the bugreport.
|
|
# Apply relaxed permissions.
|
|
chmod 777 /sys/kernel/tracing/instances/irq_gia_google
|
|
chmod 777 /sys/kernel/tracing/instances/irq_gia_google/trace
|
|
chown system system /sys/kernel/tracing/instances/irq_gia_google
|
|
chown system system /sys/kernel/tracing/instances/irq_gia_google/trace
|
|
|
|
# There are some very high frequency IRQ events happening all the time. Tracing
|
|
# them is not absolute necessity, but a flood of them is noise for more interesting
|
|
# events that we want to capture. All these high frequency IRQs have virq < 11.
|
|
write /sys/kernel/tracing/instances/irq_gia_google/events/irq/filter "irq > 11"
|
|
|
|
# Keep the buffer size small. This size is practically enough for debug purpose.
|
|
# Having low size helps because this entire buffer gets dumped in bugreport.
|
|
# Having a large size can impact bugreport size and time it takes to pack/unpack.
|
|
write /sys/kernel/tracing/instances/irq_gia_google/buffer_size_kb 16
|