c5c4f1ef81
It's been found that every GIA trace events takes about
0.7 us. GIA driver throws 5 trace events for every IRQ
via GIA. Reducing some events would make IRQ handler
flow a but more optimized.
Bug: 380463996
Test: observed the trace and the disabled trace entries
are not longer present, reducing pressure on runtime
performance as well as memory pressure on trace buffer.
Flag: EXEMPT, optimize interrupt tracing.
Change-Id: I233d82da7a6eb75344afe3798c9f850a74e5e16b
Signed-off-by: Chintan Pandya <chintanpandya@google.com>
22 lines
1.3 KiB
Text
22 lines
1.3 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
|
|
|
|
# Reduce some GIA events from interrupt handler
|
|
write /sys/kernel/tracing/instances/irq_gia_google/events/irq_gia/gia_get_power/enable 0
|
|
write /sys/kernel/tracing/instances/irq_gia_google/events/irq_gia/gia_put_power/enable 0
|
|
write /sys/kernel/tracing/instances/irq_gia_google/events/irq_gia/gia_irq_eoi/enable 0
|