Searched full:lockstep (Results 1 – 15 of 15) sorted by relevance
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 73 * @mode: Mode to configure the Cluster - Split or LockStep
392 * resets on all applicable cores for the rproc device (depending on LockStep
419 * The sequence is different between LockStep and Split modes. The LockStep
467 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
502 * The sequence is different between LockStep and Split modes, and the order
504 * of the start function. The LockStep mode requires each operation to be
634 * subsystem either in a safety/fault-tolerant LockStep mode or a performance
647 * once (in LockStep mode) or twice (in Split mode). Support for LockStep-mode
655 * They are identically configured in LockStep mode using the primary Core0
656 * settings. However, some individual settings cannot be set in LockStep mode.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 15 either in a LockStep mode providing safety/fault tolerance features or in a
61 Should be either a value of 1 (LockStep mode) or 0 (Split mode),
62 default is LockStep mode if omitted.
120 # The following properties are mandatory for R5F Core0 in both LockStep and Split
122 # R5F Core1 in LockStep mode:
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | edac.rst | 45 same branch can be used in single mode or in lockstep mode. When
46 lockstep is enabled, the cacheline is doubled, but it generally brings
|
| /kernel/linux/linux-5.10/drivers/edac/ |
| D | i7300_edac.c | 644 * In normal or mirrored mode, it uses Lockstep mode, in decode_mtr()
656 edac_dbg(2, "\t\tECC code is on Lockstep mode\n"); in decode_mtr()
|
| D | ghes_edac.c | 460 p += sprintf(p, "Loss of Lockstep "); in ghes_edac_report_mem_error()
|
| D | sb_edac.c | 1687 /* KNL doesn't support mirroring or lockstep, in get_dimm_config()
1732 edac_dbg(0, "Lockstep is enabled\n"); in get_dimm_config()
1736 edac_dbg(0, "Lockstep is disabled\n"); in get_dimm_config()
3085 * FIXME: On some memory configurations (mirror, lockstep), the in sbridge_mce_output_error()
|
| D | i5400_edac.c | 22 * 2 channels operating in lockstep no-mirror mode. Each channel can have up to
|
| /kernel/linux/linux-5.10/arch/x86/events/ |
| D | rapl.c | 636 * Divide interval by 2 to avoid lockstep (2 * 100) in rapl_check_hw_unit()
|
| /kernel/linux/linux-5.10/arch/x86/kernel/cpu/mtrr/ |
| D | mtrr.c | 221 * the rendezvous handler is started on each CPU. And in lockstep they
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/vc4/ |
| D | vc4_crtc.c | 141 * in active scanout the HVS and PV work in lockstep wrt. HVS in vc4_crtc_get_scanout_position()
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | i915_request.c | 1759 * frame of the gpu. If the client is running in lockstep with the gpu, in i915_request_wait()
|
| /kernel/linux/linux-5.10/mm/ |
| D | memblock.c | 984 * in lockstep and returns each intersection.
|
| D | compaction.c | 1233 * lockstep.
|
| D | slab.c | 507 * the CPUs getting into lockstep and contending for the global cache chain
|
| /kernel/linux/linux-5.10/arch/x86/kvm/ |
| D | x86.c | 2525 * in lockstep.
|