| /linux/tools/testing/selftests/ftrace/test.d/kprobe/ |
| H A 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
|
| /linux/Documentation/process/ |
| H A 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.
|
| /linux/Documentation/trace/ |
| H A D | kprobes.rst | 54 probes work and how jump optimization works. They explain certain
181 When a probe is registered, before attempting this optimization,
221 Pre-optimization
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.
279 Without optimization, the pre_handler can change the kernel's execution
282 tweak the kernel's execution path, you need to suppress optimization,
[all …]
|
| H A D | ftrace-design.rst | 76 case). This is of course an optimization and not a hard requirement.
211 pointer under different optimization levels, then ignore this option.
|
| /linux/Documentation/virt/ |
| H A D | paravirt_ops.rst | 27 - indirect call which allows optimization with binary patch
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | request_firmware.rst | 60 Some devices have an optimization in place to enable the firmware to be
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_user_helpers.rst | 146 optimization in the calling code.
240 optimization in the calling code.
|
| /linux/scripts/ |
| H A D | Makefile.warn | 151 KBUILD_CFLAGS += -Wdisabled-optimization
|
| /linux/Documentation/litmus-tests/ |
| H A D | README | 58 Note also that this "roach motel" optimization is emulated by
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | idpf.rst | 82 optimization is required, we recommend experimenting with the following
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-cdc_ncm | 17 between USB bus bandwidth and device DMA optimization.
|
| /linux/Documentation/arch/arm/omap/ |
| H A D | omap_pm.rst | 108 is intended as an optimization to allow drivers to determine whether the
|
| /linux/arch/m68k/kernel/ |
| H A D | entry.S | 184 addql #1,%d0 | optimization for cmpil #-1,%d0
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | todo.rst | 119 3) Additional performance testing and optimization using iozone and similar -
|
| /linux/Documentation/scheduler/ |
| H A D | sched-ext.rst | 284 invoked. This serves two purposes. First, CPU selection optimization
287 The CPU selected by ``ops.select_cpu()`` is an optimization hint and not
442 ops.select_cpu(); /* Called on wakeup (optimization) */
|
| /linux/Documentation/driver-api/md/ |
| H A D | raid5-cache.rst | 85 checksum is an optimization because MD can write meta and data freely without
|
| /linux/drivers/pci/ |
| H A D | Kconfig | 201 TPH allows endpoint devices to provide optimization hints, such as
|
| /linux/Documentation/block/ |
| H A D | blk-mq.rst | 22 any layer on the storage stack. One example of such optimization technique
|
| /linux/Documentation/crypto/ |
| H A D | descore-readme.rst | 396 you should edit the Makefile with the appropriate optimization flags
397 for your compiler (MAX optimization).
|
| /linux/Documentation/timers/ |
| H A D | hrtimers.rst | 72 special-purpose optimization of the existing timer wheel for the low
|
| /linux/Documentation/core-api/ |
| H A D | memory-allocation.rst | 104 the request is a performance optimization and there is another
|
| /linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 640 optimization transparently when upgrading their kernels.
654 A: Although LLVM IR generation and optimization try to stay architecture
669 The bpf target does not support switch table optimization.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | control-dependencies.txt | 74 optimization levels:
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | tsx_async_abort.rst | 40 those buffers can be forwarded to load operations as an optimization.
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 18 dependent load (store-to-load forwarding) as an optimization. The forward
|