blob: 52fcaa539e65feaf9811204128f8116d88bbad7a [file] [log] [blame]
Chintan Pandyad6b9cc42024-11-15 09:22:42 -08001on init
2 # Create the directory for the trace instance during early init
Chintan Pandya2d6b42c2024-12-05 18:21:02 +00003 chmod 666 /sys/kernel/tracing/instances/irq_gia_google
4 chmod 666 /sys/kernel/tracing/instances/irq_gia_google/trace
Chintan Pandyad6b9cc42024-11-15 09:22:42 -08005 chown system system /sys/kernel/tracing/instances/irq_gia_google
6 chown system system /sys/kernel/tracing/instances/irq_gia_google/trace
7
Chintan Pandyad6b9cc42024-11-15 09:22:42 -08008 # There are some very high frequency IRQ events happening all the time. Tracing
9 # them is not absolute necessity, but a flood of them is noise for more interesting
10 # events that we want to capture. All these high frequency IRQs have virq < 11.
11 write /sys/kernel/tracing/instances/irq_gia_google/events/irq/filter "irq > 11"
Chintan Pandyad6b9cc42024-11-15 09:22:42 -080012
13 # Keep the buffer size small. This size is practically enough for debug purpose.
14 # Having low size helps because this entire buffer gets dumped in bugreport.
15 # Having a large size can impact bugreport size and time it takes to pack/unpack.
16 write /sys/kernel/tracing/instances/irq_gia_google/buffer_size_kb 512