Mercurial > flash_v2
comparison packages/kernel/current/cdl/instrument.cdl @ 76:435cced73e2f ecos-v1_3_1-release
eCos v1.3.1 merged from eCos master repository on 2000-03-27-23:22:51-BST
| author | jlarmour |
|---|---|
| date | Tue, 28 Mar 2000 14:10:45 +0000 |
| parents | |
| children | 518f42066aba |
comparison
equal
deleted
inserted
replaced
| 75:41bf073c0c32 | 76:435cced73e2f |
|---|---|
| 1 # ==================================================================== | |
| 2 # | |
| 3 # instrument.cdl | |
| 4 # | |
| 5 # configuration data related to the kernel instrumentation | |
| 6 # | |
| 7 # ==================================================================== | |
| 8 #####COPYRIGHTBEGIN#### | |
| 9 # | |
| 10 # ------------------------------------------- | |
| 11 # The contents of this file are subject to the Red Hat eCos Public License | |
| 12 # Version 1.1 (the "License"); you may not use this file except in | |
| 13 # compliance with the License. You may obtain a copy of the License at | |
| 14 # http://www.redhat.com/ | |
| 15 # | |
| 16 # Software distributed under the License is distributed on an "AS IS" | |
| 17 # basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the | |
| 18 # License for the specific language governing rights and limitations under | |
| 19 # the License. | |
| 20 # | |
| 21 # The Original Code is eCos - Embedded Configurable Operating System, | |
| 22 # released September 30, 1998. | |
| 23 # | |
| 24 # The Initial Developer of the Original Code is Red Hat. | |
| 25 # Portions created by Red Hat are | |
| 26 # Copyright (C) 1998, 1999, 2000 Red Hat, Inc. | |
| 27 # All Rights Reserved. | |
| 28 # ------------------------------------------- | |
| 29 # | |
| 30 #####COPYRIGHTEND#### | |
| 31 # ==================================================================== | |
| 32 ######DESCRIPTIONBEGIN#### | |
| 33 # | |
| 34 # Author(s): jskov | |
| 35 # Original data: nickg | |
| 36 # Contributors: | |
| 37 # Date: 1999-07-05 | |
| 38 # | |
| 39 #####DESCRIPTIONEND#### | |
| 40 # | |
| 41 # ==================================================================== | |
| 42 | |
| 43 | |
| 44 cdl_option CYGNUM_KERNEL_INSTRUMENT_BUFFER_SIZE { | |
| 45 display "Size of instrumentation buffer size" | |
| 46 flavor data | |
| 47 legal_values 16 to 0x100000 | |
| 48 default_value 256 | |
| 49 description " | |
| 50 If kernel instrumentation is enabled then the instrumentation | |
| 51 data goes into a circular buffer. A larger buffer allows | |
| 52 more data to be stored, but at a significant cost in memory. | |
| 53 The value of this option corresponds to the number of entries | |
| 54 in the table, and typically each entry will require 16 bytes | |
| 55 of memory." | |
| 56 } | |
| 57 | |
| 58 cdl_option CYGNUM_KERNEL_INSTRUMENT_BUFFER_WRAP { | |
| 59 display "Wrap instrument buffer" | |
| 60 default_value 1 | |
| 61 description " | |
| 62 When the instrumentation buffer is full it can either be restarted | |
| 63 from the beginning, overwriting older data, or it can stop at the | |
| 64 end. The former is useful if you want to look at the last entries | |
| 65 made while the latter is useful if you want to look at the first | |
| 66 few." | |
| 67 } | |
| 68 | |
| 69 cdl_option CYGDBG_KERNEL_INSTRUMENT_FLAGS { | |
| 70 display "Perform selective instrumentation" | |
| 71 default_value 1 | |
| 72 description " | |
| 73 The kernel can either collect all instrumentation events, or | |
| 74 it can filter out events at runtime based on a set of flags. | |
| 75 For example it would be possible to decide at runtime that | |
| 76 only scheduler and interrupt instrumentation flags are of | |
| 77 interest and that all other flags should be ignored. This | |
| 78 flag mechanism involves extra code and processor cycle | |
| 79 overhead in the instrumentation code, so it can be disabled | |
| 80 if the application developer is interested in all | |
| 81 instrumentation events." | |
| 82 } | |
| 83 | |
| 84 cdl_option CYGDBG_KERNEL_INSTRUMENT_SCHED { | |
| 85 display "Instrument the scheduler" | |
| 86 default_value 1 | |
| 87 active_if CYGPKG_KERNEL_SCHED | |
| 88 description " | |
| 89 It is possible to perform selective instrumentation at | |
| 90 run-time. It is also possible to disable instrumentation | |
| 91 in various kernel components at compile-time, thus | |
| 92 reducing the code size overheads. This option controls | |
| 93 whether or not instrumentation support is compiled into | |
| 94 the scheduling code." | |
| 95 } | |
| 96 | |
| 97 cdl_option CYGDBG_KERNEL_INSTRUMENT_THREAD { | |
| 98 display "Instrument thread operations" | |
| 99 default_value 1 | |
| 100 active_if CYGPKG_KERNEL_THREADS | |
| 101 description " | |
| 102 It is possible to perform selective instrumentation at | |
| 103 run-time. It is also possible to disable instrumentation | |
| 104 in various kernel components at compile-time, thus | |
| 105 reducing the code size overheads. This option controls | |
| 106 whether or not instrumentation support is compiled into | |
| 107 the code that manipulates threads." | |
| 108 } | |
| 109 | |
| 110 cdl_option CYGDBG_KERNEL_INSTRUMENT_INTR { | |
| 111 display "Instrument interrupts" | |
| 112 default_value 1 | |
| 113 active_if CYGPKG_KERNEL_INTERRUPTS | |
| 114 description " | |
| 115 It is possible to perform selective instrumentation at | |
| 116 run-time. It is also possible to disable instrumentation | |
| 117 in various kernel components at compile-time, thus | |
| 118 reducing the code size overheads. This option controls | |
| 119 whether or not instrumentation support is compiled into | |
| 120 the interrupt handling code." | |
| 121 } | |
| 122 | |
| 123 cdl_option CYGDBG_KERNEL_INSTRUMENT_MUTEX { | |
| 124 display "Instrument mutex operations" | |
| 125 default_value 1 | |
| 126 active_if CYGPKG_KERNEL_SYNCH | |
| 127 description " | |
| 128 It is possible to perform selective instrumentation at | |
| 129 run-time. It is also possible to disable instrumentation | |
| 130 in various kernel components at compile-time, thus | |
| 131 reducing the code size overheads. This option controls | |
| 132 whether or not instrumentation support is compiled into | |
| 133 the mutex code." | |
| 134 } | |
| 135 | |
| 136 cdl_option CYGDBG_KERNEL_INSTRUMENT_CONDVAR { | |
| 137 display "Instrument condition variable operations" | |
| 138 default_value 1 | |
| 139 active_if CYGPKG_KERNEL_SYNCH | |
| 140 description " | |
| 141 It is possible to perform selective instrumentation at | |
| 142 run-time. It is also possible to disable instrumentation | |
| 143 in various kernel components at compile-time, thus | |
| 144 reducing the code size overheads. This option controls | |
| 145 whether or not instrumentation support is compiled into | |
| 146 the condition variable code." | |
| 147 } | |
| 148 | |
| 149 cdl_option CYGDBG_KERNEL_INSTRUMENT_BINSEM { | |
| 150 display "Instrument binary semaphore operations" | |
| 151 default_value 1 | |
| 152 active_if CYGPKG_KERNEL_SYNCH | |
| 153 description " | |
| 154 It is possible to perform selective instrumentation at | |
| 155 run-time. It is also possible to disable instrumentation | |
| 156 in various kernel components at compile-time, thus | |
| 157 reducing the code size overheads. This option controls | |
| 158 whether or not instrumentation support is compiled into | |
| 159 the binary semaphore code." | |
| 160 } | |
| 161 | |
| 162 cdl_option CYGDBG_KERNEL_INSTRUMENT_CNTSEM { | |
| 163 display "Instrument counting semaphore operations" | |
| 164 default_value 1 | |
| 165 active_if CYGPKG_KERNEL_SYNCH | |
| 166 description " | |
| 167 It is possible to perform selective instrumentation at | |
| 168 run-time. It is also possible to disable instrumentation | |
| 169 in various kernel components at compile-time, thus | |
| 170 reducing the code size overheads. This option controls | |
| 171 whether or not instrumentation support is compiled into | |
| 172 the counting semaphore code." | |
| 173 } | |
| 174 | |
| 175 cdl_option CYGDBG_KERNEL_INSTRUMENT_MBOXT { | |
| 176 display "Instrument message box operations" | |
| 177 default_value 1 | |
| 178 active_if CYGPKG_KERNEL_SYNCH | |
| 179 description " | |
| 180 It is possible to perform selective instrumentation at | |
| 181 run-time. It is also possible to disable instrumentation | |
| 182 in various kernel components at compile-time, thus | |
| 183 reducing the code size overheads. This option controls | |
| 184 whether or not instrumentation support is compiled into | |
| 185 the message box code." | |
| 186 } | |
| 187 | |
| 188 cdl_option CYGDBG_KERNEL_INSTRUMENT_CLOCK { | |
| 189 display "Instrument clock operations" | |
| 190 default_value 1 | |
| 191 active_if CYGVAR_KERNEL_COUNTERS_CLOCK | |
| 192 description " | |
| 193 It is possible to perform selective instrumentation at | |
| 194 run-time. It is also possible to disable instrumentation | |
| 195 in various kernel components at compile-time, thus | |
| 196 reducing the code size overheads. This option controls | |
| 197 whether or not instrumentation support is compiled into | |
| 198 the real-time clock code." | |
| 199 } | |
| 200 | |
| 201 cdl_option CYGDBG_KERNEL_INSTRUMENT_ALARM { | |
| 202 display "Instrument alarm-related operations" | |
| 203 default_value 1 | |
| 204 active_if CYGVAR_KERNEL_COUNTERS_CLOCK | |
| 205 description " | |
| 206 It is possible to perform selective instrumentation at | |
| 207 run-time. It is also possible to disable instrumentation | |
| 208 in various kernel components at compile-time, thus | |
| 209 reducing the code size overheads. This option controls | |
| 210 whether or not instrumentation support is compiled into | |
| 211 the code related to alarm operations." | |
| 212 } | |
| 213 | |
| 214 cdl_option CYGDBG_KERNEL_INSTRUMENT_USER { | |
| 215 display "Support application-level instrumentation" | |
| 216 default_value 1 | |
| 217 description " | |
| 218 It is possible to perform selective instrumentation at | |
| 219 run-time. It is also possible to disable instrumentation | |
| 220 in various kernel components at compile-time, thus | |
| 221 reducing the code size overheads. This option controls | |
| 222 whether or not application-level instrumentation gets | |
| 223 compiled in." | |
| 224 } |
