| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117 |
- config MTPROF
- bool "Enable MTK profiler/debugger tool"
- help
- CONFIG_MTPROF define if mtk profiling tools should be built-in or not. It
- includes workqueue debugger, signal debugger, cputime, bootprof, and other
- misc tools. If you are not sure about whether to enable it or not, please
- set n.
- if MTPROF
- config MTK_LOCK_DEBUG
- bool "Support some MTK lock debug patches"
- default y
- help
- CONFIG_MTK_LOCK_DEBUG is used to catch db when spinlock spin more than 1s and to catch
- db when check lock fail,such as bug_header,circular_bug,deadlock_bug and so on
- Say Y here to enable, If you are not sure about whether to enable it or not, please
- set n.
- config MTPROF_CPUTIME
- bool "thread cputime profiling"
- depends on SCHEDSTATS
- help
- CONFIG_MTPROF_CPUTIME is used to measure process/irq execution time and export
- the information in /proc/mtprof/cputime. Say Y here to enable thread cputime
- profiling. If you are not sure about whether to enable it or not, please
- set n.
- config MTK_WQ_DEBUG
- bool "mtk workqueue debug"
- help
- CONFIG_MTK_WQ_DEBUG define if workqueue debugging should be built-in or not
- It will add logs to monitor work activation, queue, and execution. Say y to
- enable mtk workqueue debug, or if you are not sure about this, please
- set n
- config MT_SCHED_MONITOR
- bool "mt scheduler monitor"
- default n
- help
- MT_SCHED_MONITOR is used to monitor ISR/SOFTIRQ/TASKLET/HRTIMER/STIMER
- disable duration. Say Y here to enable ISR/SOFTIRQ/TASKLET/HRTIMER/STIMER
- monitor. If you are not sure about whether to enable it or not, please
- set n.
- config MT_SCHED_MON_DEFAULT_ENABLE
- bool "default enable mt scheduler monitor"
- depends on MT_SCHED_MONITOR
- default n
- help
- MT_SCHED_MON_DEFAULT_ENABLE is used to enable scheduler monitor for auto test
- system performance(ISR/SOFTIRQ/TASKLET/HRTIMER/STIMER). Say Y here to
- enable auto test scheduler monitor. If you are not sure about whether
- to enable it or not, please set n.
- config MT_RT_THROTTLE_MON
- bool "mt rt throttle monitor"
- default n
- help
- MT_RT_THROTTLE_MON is used to monitor rt throttle. When rt throttle activated
- print 5 longest execusion time rt tasks. Say Y here to enable rt throttle
- monitor. If you are not sure about whether to enable it or not, please set n.
- config PREEMPT_MONITOR
- bool "mt preempt monitor"
- default n
- help
- PREEMPT_MONITOR is used to monitor PREEMPT disable/enalbe and
- local_irq_disable/enable duration. Say Y here to enable PREEMPT and
- local_irq_disable/enable monitor.
- If you are not sure about whether to enable it or not, please set n.
- config PRINTK_PROCESS_INFO
- bool "Prefix pid/process_name to each kernel log"
- default y
- help
- PRINTK_PROCESS_INFO which is used to control whether to show
- process information about this log.
- the information about which cpu about this
- process in, and whether in isr.
- config MT_PRINTK_UART_CONSOLE
- bool "MTK printk UART controller"
- default y
- help
- MT_PRINTK_UART_CONSOLE which is used to control whether to
- control printk to uart console. when boot up finish
- uart console do not output printk log.
- also RD can set the setting by command.
- config LOG_TOO_MUCH_WARNING
- bool "printk too much warning"
- default y
- help
- LOG_TOO_MUCH_WARNING which is used to control whether to
- detect printk too much issue. kernel log too much will detect and
- create a exception when printk log large than
- LOG_TOO_MUCH_DETECT_COUNT in one second.
- config LOG_TOO_MUCH_DETECT_COUNT
- hex "printk too much detect count"
- default 0xC8
- depends on LOG_TOO_MUCH_WARNING
- config LOG_TOO_MUCH_DETECT_GAP
- hex "detect log too much delay time"
- default 10
- depends on LOG_TOO_MUCH_WARNING
- config MT_BOOT_TIME_CPU_BOOST
- bool "Boost CPU performance to enhance boot speed"
- default y
- help
- MT_BOOT_TIME_CPU_BOOST is to boost CPU performance to enhance boot
- speed and save time cost during system booting. This mechanism
- will recover DVFS/hotplug after system boot up done.
- endif
|