Lines Matching +full:high +full:- +full:performance
1 # SPDX-License-Identifier: GPL-2.0-only
12 flaws, this plugin is available to identify and zero-initialize
23 def_bool $(cc-option,-ftrivial-auto-var-init=pattern)
26 …def_bool $(cc-option,-ftrivial-auto-var-init=zero -enable-trivial-auto-var-init-zero-knowing-it-wi…
37 variables initialized), but the performance impact depends
54 bool "zero-init structs marked for userspace (weak)"
58 Zero-initialize any structures on the stack containing
61 exposures, like CVE-2013-2141:
65 bool "zero-init structs passed by reference (strong)"
70 Zero-initialize any structures on the stack that may
74 exposures, like CVE-2017-1000410:
77 As a side-effect, this keeps a lot of variables on the
83 bool "zero-init anything passed by reference (very strong)"
88 Zero-initialize any stack variables that may be passed
95 bool "0xAA-init everything on the stack (strongest)"
106 non-NULL values, buffer sizes and indices are very big.
109 bool "zero-init everything on the stack (strongest and safest)"
146 most uninitialized stack variable attacks, with the performance
150 The performance impact on a single CPU system kernel compilation
180 can be useful for estimating the STACKLEAK performance impact for
199 heap content exposures. The performance impact varies by
201 workloads have measured as high as 7%.
215 The performance impact varies by workload, but is more expensive
217 touching "cold" memory areas. Most cases see 3-5% impact. Some
218 synthetic workloads have measured as high as 8%.