📄 instrument.cdl
字号:
# ====================================================================## instrument.cdl## configuration data related to the kernel instrumentation## ====================================================================#####COPYRIGHTBEGIN##### # ------------------------------------------- # The contents of this file are subject to the Red Hat eCos Public License # Version 1.1 (the "License"); you may not use this file except in # compliance with the License. You may obtain a copy of the License at # http://www.redhat.com/ # # Software distributed under the License is distributed on an "AS IS" # basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the # License for the specific language governing rights and limitations under # the License. # # The Original Code is eCos - Embedded Configurable Operating System, # released September 30, 1998. # # The Initial Developer of the Original Code is Red Hat. # Portions created by Red Hat are # Copyright (C) 1998, 1999, 2000 Red Hat, Inc. # All Rights Reserved. # ------------------------------------------- # #####COPYRIGHTEND##### ====================================================================######DESCRIPTIONBEGIN###### Author(s): jskov# Original data: nickg# Contributors:# Date: 1999-07-05######DESCRIPTIONEND###### ====================================================================cdl_option CYGNUM_KERNEL_INSTRUMENT_BUFFER_SIZE { display "Size of instrumentation buffer size" flavor data legal_values 16 to 0x100000 default_value 256 description " If kernel instrumentation is enabled then the instrumentation data goes into a circular buffer. A larger buffer allows more data to be stored, but at a significant cost in memory. The value of this option corresponds to the number of entries in the table, and typically each entry will require 16 bytes of memory."}cdl_option CYGNUM_KERNEL_INSTRUMENT_BUFFER_WRAP { display "Wrap instrument buffer" default_value 1 description " When the instrumentation buffer is full it can either be restarted from the beginning, overwriting older data, or it can stop at the end. The former is useful if you want to look at the last entries made while the latter is useful if you want to look at the first few."}cdl_option CYGDBG_KERNEL_INSTRUMENT_FLAGS { display "Perform selective instrumentation" default_value 1 description " The kernel can either collect all instrumentation events, or it can filter out events at runtime based on a set of flags. For example it would be possible to decide at runtime that only scheduler and interrupt instrumentation flags are of interest and that all other flags should be ignored. This flag mechanism involves extra code and processor cycle overhead in the instrumentation code, so it can be disabled if the application developer is interested in all instrumentation events."}cdl_option CYGDBG_KERNEL_INSTRUMENT_SCHED { display "Instrument the scheduler" default_value 1 active_if CYGPKG_KERNEL_SCHED description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the scheduling code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_THREAD { display "Instrument thread operations" default_value 1 active_if CYGPKG_KERNEL_THREADS description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the code that manipulates threads."}cdl_option CYGDBG_KERNEL_INSTRUMENT_INTR { display "Instrument interrupts" default_value 1 active_if CYGPKG_KERNEL_INTERRUPTS description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the interrupt handling code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_MUTEX { display "Instrument mutex operations" default_value 1 active_if CYGPKG_KERNEL_SYNCH description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the mutex code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_CONDVAR { display "Instrument condition variable operations" default_value 1 active_if CYGPKG_KERNEL_SYNCH description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the condition variable code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_BINSEM { display "Instrument binary semaphore operations" default_value 1 active_if CYGPKG_KERNEL_SYNCH description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the binary semaphore code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_CNTSEM { display "Instrument counting semaphore operations" default_value 1 active_if CYGPKG_KERNEL_SYNCH description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the counting semaphore code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_MBOXT { display "Instrument message box operations" default_value 1 active_if CYGPKG_KERNEL_SYNCH description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the message box code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_CLOCK { display "Instrument clock operations" default_value 1 active_if CYGVAR_KERNEL_COUNTERS_CLOCK description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the real-time clock code."}cdl_option CYGDBG_KERNEL_INSTRUMENT_ALARM { display "Instrument alarm-related operations" default_value 1 active_if CYGVAR_KERNEL_COUNTERS_CLOCK description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not instrumentation support is compiled into the code related to alarm operations."}cdl_option CYGDBG_KERNEL_INSTRUMENT_USER { display "Support application-level instrumentation" default_value 1 description " It is possible to perform selective instrumentation at run-time. It is also possible to disable instrumentation in various kernel components at compile-time, thus reducing the code size overheads. This option controls whether or not application-level instrumentation gets compiled in."}
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -