| /kernel/linux/linux-6.6/tools/testing/selftests/ftrace/test.d/kprobe/ |
| D | kprobe_opt_types.tc | 19 DEFAULT=$(cat /proc/sys/debug/kprobes-optimization)
20 echo 1 > /proc/sys/debug/kprobes-optimization
29 echo "$DEFAULT" > /proc/sys/debug/kprobes-optimization
33 echo "$DEFAULT" > /proc/sys/debug/kprobes-optimization
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | kprobes.rst | 54 probes work and how jump optimization works. They explain certain
169 How Does Jump Optimization Work?
181 When a probe is registered, before attempting this optimization,
221 Pre-optimization
242 Optimization subsection
251 of kprobe optimization supports only kernels with CONFIG_PREEMPT=n [4]_.
262 the optimization is complete, the kprobe is just dequeued from the
263 optimized list. If the optimization has been done, the jump is
273 .. [4] This optimization-safety checking may be replaced with the
278 The jump optimization changes the kprobe's pre_handler behavior.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | kprobes.rst | 54 probes work and how jump optimization works. They explain certain
170 How Does Jump Optimization Work?
182 When a probe is registered, before attempting this optimization,
222 Pre-optimization
243 Optimization subsection
252 of kprobe optimization supports only kernels with CONFIG_PREEMPT=n [4]_.
263 the optimization is complete, the kprobe is just dequeued from the
264 optimized list. If the optimization has been done, the jump is
274 .. [4] This optimization-safety checking may be replaced with the
279 The jump optimization changes the kprobe's pre_handler behavior.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | volatile-considered-harmful.rst | 15 to suppress optimization, which is almost never what one really wants to
19 all optimization-related problems in a more efficient way.
23 unwanted optimization. If they are being used properly, there will be no
42 forget anything it knows. There will be no optimization problems with
59 optimization, so, once again, volatile is unnecessary.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | volatile-considered-harmful.rst | 15 to suppress optimization, which is almost never what one really wants to
19 all optimization-related problems in a more efficient way.
23 unwanted optimization. If they are being used properly, there will be no
42 forget anything it knows. There will be no optimization problems with
59 optimization, so, once again, volatile is unnecessary.
|
| /kernel/linux/linux-6.6/arch/x86/ |
| D | Kconfig.cpu | 2 # Put here option for CPU selection and depending optimization
103 copy optimization, compiles the kernel with optimization flags
164 some extended instructions, and passes appropriate optimization
172 some extended instructions, and passes appropriate optimization
180 optimization flags to GCC.
187 like a 586 with TSC, and sets some GCC optimization flags (like a
346 # P6_NOPs are a relatively minor optimization that require a family >=
354 # the right-hand clause are the cores that benefit from this optimization.
|
| /kernel/linux/linux-5.10/arch/x86/ |
| D | Kconfig.cpu | 2 # Put here option for CPU selection and depending optimization
103 copy optimization, compiles the kernel with optimization flags
164 some extended instructions, and passes appropriate optimization
172 some extended instructions, and passes appropriate optimization
180 optimization flags to GCC.
187 like a 586 with TSC, and sets some GCC optimization flags (like a
350 # P6_NOPs are a relatively minor optimization that require a family >=
358 # the right-hand clause are the cores that benefit from this optimization.
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 71 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
77 …optimization (have Z-bit either set or pass). This is a dispatch based speculative event, and is u…
83 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
89 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 71 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
77 …optimization (have Z-bit either set or pass). This is a dispatch based speculative event, and is u…
83 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
89 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen3/ |
| D | floating-point.json | 70 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
76 …optimization (have Z-bit either set or pass). This is a dispatch based speculative event, and is u…
82 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
88 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /kernel/linux/linux-5.10/tools/power/acpi/ |
| D | Makefile.config | 61 # use '-Os' optimization if available, else use -O2
62 OPTIMIZATION := $(call cc-supports,-Os,-O2)
86 CFLAGS += $(OPTIMIZATION) -fomit-frame-pointer
|
| /kernel/linux/linux-6.6/tools/power/acpi/ |
| D | Makefile.config | 61 # use '-Os' optimization if available, else use -O2
62 OPTIMIZATION := $(call cc-supports,-Os,-O2)
87 CFLAGS += $(OPTIMIZATION) -fomit-frame-pointer
|
| /kernel/linux/linux-6.6/arch/powerpc/purgatory/ |
| D | Makefile | 8 # When profile-guided optimization is enabled, llvm emits two different
10 # optimization flags.
|
| /kernel/linux/linux-5.10/arch/powerpc/purgatory/ |
| D | Makefile | 7 # When profile-guided optimization is enabled, llvm emits two different
9 # optimization flags.
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_cache.h | 53 * only, but permits an optimization to be enabled in some cases, where in drm_arch_can_wc_memory()
61 * case. However, on ARM and arm64, enabling this optimization on a in drm_arch_can_wc_memory()
65 * optimization entirely for ARM and arm64. in drm_arch_can_wc_memory()
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_cache.h | 55 * only, but permits an optimization to be enabled in some cases, where in drm_arch_can_wc_memory()
63 * case. However, on ARM and arm64, enabling this optimization on a in drm_arch_can_wc_memory()
67 * optimization entirely for ARM and arm64. in drm_arch_can_wc_memory()
|
| /kernel/liteos_a/ |
| D | Kconfig | 64 bool "Enable code optimization options"
67 Answer Y to add optimization options for efficient code.
72 bool "Enable code size optimization options" if COMPILE_OPTIMIZE
75 Answer Y to add optimization options for small code size.
80 bool "Enable link time optimization (LTO)" if COMPILE_OPTIMIZE_SIZE
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 172 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
178 …"BriefDescription": "Number of Ops that are candidates for optimization (have Z-bit either set or …
179 …of the Move elimination and Scalar code optimization schemes. Number of Ops that are candidates fo…
186 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
193 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 172 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
178 …"BriefDescription": "Number of Ops that are candidates for optimization (have Z-bit either set or …
179 …of the Move elimination and Scalar code optimization schemes. Number of Ops that are candidates fo…
186 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
193 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
|
| /kernel/linux/linux-6.6/scripts/ |
| D | Makefile.clang | 31 # certain optimization flags it knows it has not implemented.
35 CLANG_FLAGS += -Werror=ignored-optimization-argument
|
| /kernel/linux/linux-5.10/arch/alpha/include/asm/ |
| D | elf.h | 20 #define R_ALPHA_LITERAL 4 /* GP relative 16 bit w/optimization */
21 #define R_ALPHA_LITUSE 5 /* Optimization hint for LITERAL */
136 specific libraries for optimization. This is more specific in
|
| /kernel/linux/linux-6.6/arch/alpha/include/asm/ |
| D | elf.h | 20 #define R_ALPHA_LITERAL 4 /* GP relative 16 bit w/optimization */
21 #define R_ALPHA_LITUSE 5 /* Optimization hint for LITERAL */
130 specific libraries for optimization. This is more specific in
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| D | static-keys.rst | 91 optimization.
100 In order to make use of this optimization you must first define a key::
184 to take advantage of this optimization. If there is no architecture support, we
251 Without the jump label optimization it looks like::
330 this optimization is about reducing the number of branches. In addition, we've
|
| /kernel/liteos_m/ |
| D | Kconfig | 57 bool "Enable code optimization options"
60 Answer Y to add optimization options for efficient code.
65 bool "Enable code size optimization options" if COMPILE_OPTIMIZE
68 Answer Y to add optimization options for small code size.
73 bool "Enable link time optimization (LTO)" if COMPILE_OPTIMIZE_SIZE
|
| /kernel/linux/linux-6.6/Documentation/staging/ |
| D | static-keys.rst | 91 optimization.
100 In order to make use of this optimization you must first define a key::
184 to take advantage of this optimization. If there is no architecture support, we
248 Without the jump label optimization it looks like::
327 this optimization is about reducing the number of branches. In addition, we've
|