Home
last modified time | relevance | path

Searched +full:fault +full:- +full:inject (Results 1 – 14 of 14) sorted by relevance

/Documentation/devicetree/bindings/misc/
Dxlnx,tmr-inject.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/misc/xlnx,tmr-inject.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx Triple Modular Redundancy(TMR) Inject IP
10 - Appana Durga Kedareswara rao <appana.durga.kedareswara.rao@amd.com>
13 The Triple Modular Redundancy(TMR) Inject core provides functional fault
15 possibility to verify that the TMR subsystem error detection and fault
21 - xlnx,tmr-inject-1.0
35 - compatible
[all …]
/Documentation/fault-injection/
Dfault-injection.rst2 Fault injection capabilities infrastructure
5 See also drivers/md/md-faulty.c and "every_nth" module option for scsi_debug.
8 Available fault injection capabilities
9 --------------------------------------
11 - failslab
15 - fail_page_alloc
19 - fail_usercopy
23 - fail_futex
25 injects futex deadlock and uaddr fault errors.
27 - fail_sunrpc
[all …]
Dindex.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Fault-injection
10 fault-injection
11 notifier-error-inject
12 nvme-fault-injection
13 provoke-crashes
Dnotifier-error-inject.rst4 Notifier error injection provides the ability to inject artificial errors to
15 ----------------------------------
18 /sys/kernel/debug/notifier-error-inject/pm/actions/<notifier event>/error
26 Example: Inject PM suspend error (-12 = -ENOMEM)::
28 # cd /sys/kernel/debug/notifier-error-inject/pm/
29 # echo -12 > actions/PM_SUSPEND_PREPARE/error
34 ----------------------------------------------
37 /sys/kernel/debug/notifier-error-inject/memory/actions/<notifier event>/error
44 Example: Inject memory hotplug offline error (-12 == -ENOMEM)::
46 # cd /sys/kernel/debug/notifier-error-inject/memory
[all …]
Dnvme-fault-injection.rst1 NVMe Fault Injection
3 Linux's fault injection framework provides a systematic way to support
10 Following examples show how to inject an error into the nvme.
16 Example 1: Inject default status code with no retry
17 ---------------------------------------------------
34 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-rc8+ #2
68 EXT4-fs error (device nvme0n1): ext4_find_entry:1436:
71 Example 2: Inject default status code with retry
72 ------------------------------------------------
92 CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-rc8+ #4
[all …]
/Documentation/mm/
Dhwpoison.rst41 The code consists of a the high level handler in mm/memory-failure.c,
46 of applications. KVM support requires a recent qemu-kvm release.
49 KVM can inject the machine check into the guest with the proper
109 * madvise(MADV_HWPOISON, ....) (as root) - Poison a page in the
112 * hwpoison-inject module through debugfs ``/sys/kernel/debug/hwpoison/``
114 corrupt-pfn
115 Inject hwpoison fault at PFN echoed into this file. This does
118 unpoison-pfn
119 Software-unpoison page at PFN echoed into this file. This way
127 corrupt-filter-dev-major, corrupt-filter-dev-minor
[all …]
/Documentation/virt/kvm/devices/
Ds390_flic.rst1 .. SPDX-License-Identifier: GPL-2.0
7 FLIC handles floating (non per-cpu) interrupts, i.e. I/O, service and some
8 machine check interruptions. All interrupts are stored in a per-vm list of
14 - add interrupts (KVM_DEV_FLIC_ENQUEUE)
15 - inspect currently pending interrupts (KVM_FLIC_GET_ALL_IRQS)
16 - purge all pending floating interrupts (KVM_DEV_FLIC_CLEAR_IRQS)
17 - purge one pending floating I/O interrupt (KVM_DEV_FLIC_CLEAR_IO_IRQ)
18 - enable/disable for the guest transparent async page faults
19 - register and modify adapter interrupt sources (KVM_DEV_FLIC_ADAPTER_*)
20 - modify AIS (adapter-interruption-suppression) mode state (KVM_DEV_FLIC_AISM)
[all …]
/Documentation/virt/kvm/x86/
Dmmu.rst1 .. SPDX-License-Identifier: GPL-2.0
13 - correctness:
18 - security:
21 - performance:
23 - scaling:
25 - hardware:
27 - integration:
31 - dirty tracking:
33 and framebuffer-based displays
34 - footprint:
[all …]
/Documentation/virt/hyperv/
Dcoco.rst1 .. SPDX-License-Identifier: GPL-2.0
5 Hyper-V can create and run Linux guests that are Confidential Computing
9 CoCo VMs on Hyper-V share the generic CoCo VM threat model and security
10 objectives described in Documentation/security/snp-tdx-threat-model.rst. Note
11 that Hyper-V specific code in Linux refers to CoCo VMs as "isolated VMs" or
14 A Linux CoCo VM on Hyper-V requires the cooperation and interaction of the
19 * The hardware runs a version of Windows/Hyper-V with support for CoCo VMs
25 * AMD processor with SEV-SNP. Hyper-V does not run guest VMs with AMD SME,
26 SEV, or SEV-ES encryption, and such encryption is not sufficient for a CoCo
27 VM on Hyper-V.
[all …]
/Documentation/gpu/
Ddrm-vm-bind-async.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR MIT)
10 * ``VRAM``: On-device memory. Sometimes referred to as device local memory.
16 an IOCTL. The operations include mapping and unmapping system- or
20 synchronization objects can be either generic, like dma-fences or
24 * ``in-syncobj``: Argument to a VM_BIND IOCTL, the VM_BIND operation waits
27 * ``out-syncobj``: Argument to a VM_BIND_IOCTL, the VM_BIND operation
30 * ``dma-fence``: A cross-driver synchronization object. A basic
31 understanding of dma-fences is required to digest this
33 :doc:`dma-buf doc </driver-api/dma-buf>`.
35 * ``memory fence``: A synchronization object, different from a dma-fence.
[all …]
/Documentation/virt/kvm/
Dapi.rst1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
13 - System ioctls: These query and set global attributes which affect the
17 - VM ioctls: These query and set attributes that affect an entire virtual
24 - vcpu ioctls: These query and set attributes that control the operation
32 - device ioctls: These query and set attributes that control the operation
80 facility that allows backward-compatible extensions to the API to be
104 the ioctl returns -ENOTTY.
122 -----------------------
139 -----------------
[all …]
/Documentation/trace/
Dkprobes.rst29 collect debugging and performance information non-disruptively. You
41 In the typical case, Kprobes-based instrumentation is packaged as
56 Kprobes -- e.g., the difference between a pre_handler and
62 -----------------------
74 Next, Kprobes single-steps its copy of the probed instruction.
75 (It would be simpler to single-step the actual instruction in place,
80 After the instruction is single-stepped, Kprobes executes the
85 -----------------------
105 -------------
114 is an arbitrary piece of code -- typically just a nop instruction.
[all …]
/Documentation/networking/dsa/
Ddsa.rst22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
61 - the "dsa" port(s) are just conduits between two or more switches, and as such
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]