Introduce CONFIG_STACKLEAK_METRICS providing STACKLEAK information about tasks via the /proc file system. In particular, /proc/<pid>/stack_depth shows the maximum kernel stack consumption for the current and previous syscalls. Although this information is not precise, it can be useful for estimating the STACKLEAK performance impact for your workloads.
Showing the changes to scripts (1 of 5 files). Show all
Unified · Split
| @@ -170,4 +170,16 @@ config STACKLEAK_TRACK_MIN_SIZE · 169 unmodified lines | ||
| 170 | 170 | a stack frame size greater than or equal to this parameter. |
| 171 | 171 | If unsure, leave the default value 100. |
| 172 | 172 | |
| 173 | +config STACKLEAK_METRICS | |
| 174 | + bool "Show STACKLEAK metrics in the /proc file system" | |
| 175 | + depends on GCC_PLUGIN_STACKLEAK | |
| 176 | + depends on PROC_FS | |
| 177 | + help | |
| 178 | + If this is set, STACKLEAK metrics for every task are available in | |
| 179 | + the /proc file system. In particular, /proc/<pid>/stack_depth | |
| 180 | + shows the maximum kernel stack consumption for the current and | |
| 181 | + previous syscalls. Although this information is not precise, it | |
| 182 | + can be useful for estimating the STACKLEAK performance impact for | |
| 183 | + your workloads. | |
| 184 | + | |
| 173 | 185 | endif |