Home
last modified time | relevance | path

Searched full:injecting (Results 1 – 25 of 82) sorted by relevance

1234

/linux-5.10/tools/testing/selftests/rseq/
Drun_param_test.sh73 echo "Injecting at <${INJECT_LIST[$i]}>"
94 echo "Injecting at <${INJECT_LIST[$i]}>"
/linux-5.10/tools/testing/selftests/powerpc/scripts/
Dhmi.sh59 echo "Injecting HMI on core $core, chip $chip" | tee /dev/kmsg
62 echo "Error injecting. Aborting!"
/linux-5.10/tools/testing/fault-injection/
Dfailcmd.sh5 # failcmd.sh - run a command with injecting slab/page allocation failures
12 # Run command with injecting slab/page allocation failures by fault
/linux-5.10/include/linux/
Dfault-inject-usercopy.h6 * This header provides a wrapper for injecting failures to user space memory
Denergy_model.h149 * By injecting (1) in (2), 'cpu_nrg' can be re-expressed as a product in em_cpu_energy()
/linux-5.10/drivers/net/ethernet/freescale/fman/
DKconfig39 stress with multiple ports injecting line-rate traffic.
/linux-5.10/tools/perf/Documentation/
Dperf-inject.txt62 Process jitdump files by injecting the mmap records corresponding to jitted
/linux-5.10/tools/testing/selftests/arm64/signal/
DREADME38 kind of tests it is extremely easy in fact to end-up injecting other
/linux-5.10/lib/
Dnotifier-error-inject.c42 pr_info("Injecting error (%d) to %s\n", err, action->name); in notifier_err_inject_callback()
Dtest_blackhole_dev.c5 * by injecting an skb into the stack with skb->dev as the
/linux-5.10/samples/pktgen/
Dpktgen_bench_xmit_mode_queue_xmit.sh8 # Script for injecting packets into egress qdisc path of the stack
Dpktgen_bench_xmit_mode_netif_receive.sh7 # Script for injecting packets into RX path of the stack with pktgen
/linux-5.10/mm/
Dhwpoison-inject.c50 pr_info("Injecting memory failure at pfn %#lx\n", pfn); in hwpoison_inject()
/linux-5.10/tools/testing/selftests/powerpc/eeh/
Deeh-basic.sh53 # and injecting new errors during the recovery process will probably
/linux-5.10/drivers/powercap/
Didle_inject.c52 * @tsk: task injecting the idle cycles
204 pr_debug("Starting injecting idle cycles on CPUs '%*pbl'\n", in idle_inject_start()
/linux-5.10/drivers/gpu/drm/i915/
Di915_utils.c75 "Injecting failure %d at checkpoint %u [%s:%d]\n", in __i915_inject_probe_error()
/linux-5.10/arch/arm64/kvm/vgic/
Dvgic.c49 * Since the VGIC must support injecting virtual interrupts from ISRs, we have
51 * spinlocks for any lock that may be taken while injecting an interrupt.
537 * subsystems injecting mapped interrupts should reset their interrupt lines
895 * taking any lock. There is a potential race with someone injecting in kvm_vgic_flush_hwstate()
Dvgic-irqfd.c124 * Injecting SPIs is always possible in atomic context in kvm_arch_set_irq_inatomic()
/linux-5.10/Documentation/devicetree/bindings/thermal/
Dthermal-idle.yaml15 mitigate the temperature on the device by injecting idle cycles,
/linux-5.10/Documentation/ABI/testing/
Ddev-kmsg8 Injecting messages:
/linux-5.10/Documentation/fault-injection/
Dfault-injection.rst321 echo "Injecting errors into the module $module... (interrupt to stop)"
372 Run a command "make -C tools/testing/selftests/ run_tests" with injecting slab
/linux-5.10/drivers/edac/
Damd64_edac_inj.c88 * store 16 bit error injection vector which enables injecting errors to the
/linux-5.10/arch/x86/kernel/cpu/mce/
Dinject.c558 * This denotes into which bank we're injecting and triggers
626 "\t before injecting.\n"
/linux-5.10/Documentation/driver-api/thermal/
Dcpu-idle-cooling.rst47 At a specific OPP, we can assume that injecting idle cycle on all CPUs
/linux-5.10/Documentation/firmware-guide/acpi/apei/
Deinj.rst72 write should be the last step when injecting errors.

1234